Re: Manually Register MyODBC?
Mike Harknett <[email protected]>
| Newsgroups | gmane.comp.db.mysql.odbc |
|---|---|
| Message-ID | <[email protected]> |
Hi Daniel, below the .reg file that I use to add a system dsn..obviously modify to suit... don't know if it will be aNy use cheers mike Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\MAPMYSQL] "Driver"="C:\\WINDOWS\\system32\\myodbc3.dll" "DATABASE"="mysqldatabase" "DESCRIPTION"="MySQL Db for MAP" "PWD"="mysqlpwd" "SERVER"="lmysqlserver" "UID"="mysqluser" "OPTION"="515" [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources] "MAPMYSQL"="MySQL ODBC 3.51 Driver" Daniel Kasak wrote: > On Thu, 2007-05-24 at 01:55 -0500, Jess Balint wrote: > > >> On Thu, May 24, 2007 at 04:26:43PM +1000, Daniel Kasak wrote: >> >>>> There should be a utility called myodbc3i.exe that can register the >>>> driver. >>>> >>> Yeah I've tried that one too. Didn't do anything. >>> >> Any error message? >> > > No. Fails basically silently: > > dkasak@dkasak > ~/documents/myodbc/mysql-connector-odbc-noinstall-3.51.15-win32/bin $ > ~/.cxoffice/bin/wine myodbc3i.exe > Using the default (win98) bottle. > libGL warning: 3D driver claims to not support visual 0x62 > dkasak@dkasak > ~/documents/myodbc/mysql-connector-odbc-noinstall-3.51.15-win32/bin $ > > ( sorry about text wrapping ) > > >>> But it still doesn't work. I get an error: >>> >>> The setup routines for the MySQL ODBC 3.51 Driver ODBC driver could not >>> be loaded due to system error code 126. >>> >>> ... and then another error: >>> >>> Could not load the setup or translator library. >>> >> I've seen this error before, but I think it was due to the setup library >> either missing or referencing the wrong path. You might not need the >> setup lib if you also create the DSNs with myodbc3i.exe or enter them >> directly into the registry. >> > > DSNs in the registry, eh? I'll look at another Windows box and see if I > can do this, but I don't hold out much hope. > > >>> I tested this a couple of years ago, and had it working ... 3.51.06 or >>> so ... but I can't use this version because it can't authenticate >>> against newer MySQL servers. >>> >> I'm not sure if any changes would prevent this. Also, you know there is >> an 'old password' feature that allows older clients to connect? >> > > Yeah I know. At the moment, that's at the bottom of the list of options, > but the list is getting smaller quickly ... > > -- > Daniel Kasak > IT Developer > NUS Consulting Group > Level 5, 77 Pacific Highway > North Sydney, NSW, Australia 2060 > T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 > email: [email protected] > website: http://www.nusconsulting.com.au > > > -- MySQL ODBC Mailing List For list archives: http://lists.mysql.com/myodbc To unsubscribe: http://lists.mysql.com/[email protected]