Hi !!!! > -----Original Message----- > From: Adam Douglas [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 23, 2001 12:55 PM > To: 'David Turner'; '[EMAIL PROTECTED]'; Mysql@Lists. Mysql. Com (E-mail); > '[EMAIL PROTECTED]' > Subject: MySQL with MyODBC & Access > > > I've recently setup MyODBC and MS Access to use a ODBC profile that > is global to everyone. What I did was make a new user in MySQL and then > create a MyODBC User DSN. I made the links to MySQL in Access using this > profile. The problem I'm having is this, when you initially go into MS > Access you have to always click on a specific table then close it and begin > the task you wish to do. If you do not do this then nothing works. For some > odd reason if you try to open a form or a link it will come up with the ODBC > dialog box and always seems to have the database name wrong. The database > name seems to match the DSN name. Any ideas why this is not working properly > for me? If you need any more information please let me know. Oh yeah the > part that makes this really odd is that I have a User DSN setup for myself > and one other person for administration purposes only. This User DSN seems > to work fine on both our machines. Really odd.
This is due to invalid connection parameters supplied in the DSN entries. for a particular MyODBC DSN, you might have specified only the valid DSN and other fields you left it as blank, and that's why driver behaves as you explained above. Please refer to the following link, for more information on how to setup a DSN for MyODBC with different connection parameters. http://www.mysql.com/documentation/mysql/bychapter/manual_Clients.html#ODBC_adm inistrator > > Also I've noticed that using Access as a front end to MySQL it seems > to not bring through data that is using a type of bigint. Is this a > limitation of using Access as a front end? If so what other column types > would MS Access not support? As per the ODBC spec, BIGINT is not a privileged data type with 2.x specifications, so MyODBC doesn't support this. The new MyODBC 3.51 which is going to be released shortly supports BIGINT. For more information about Access-->MySQL data types, refer to the following thread: http://lists.mysql.com/cgi-ez/ezmlm-cgi?4:mss:7537:200110:nbhnfhhlmikphfjkncdh Regards, venu -- For technical support contracts, go to https://order.mysql.com __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Venu <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Developer /_/ /_/\_, /___/\___\_\___/ California, USA <___/ www.mysql.com --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
