Re: Manually Register MyODBC?

Jess Balint <[email protected]>
Newsgroups gmane.comp.db.mysql.odbc
Message-ID <[email protected]>
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?

> > Otherwise the registry detail is like so:
> > 
> > [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\MySQL ODBC 3.51 Driver]
> > "UsageCount"=dword:00000001
> 
> What's this? Is it a string?
> I'm not a registry hacker ...

The part inside the brackets is the path in the registry. You can
probably just copy that snippet from my original mail into a .reg file
and import it into the registry.

> > "Driver"="C:\\WINDOWS\\system32\\myodbc3.dll"
> > "Setup"="C:\\WINDOWS\\system32\\myodbc3S.dll"
> > "CPTimeout"="<not pooled>"
> 
> This bit I follow ...
> 
> 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.

> 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?

Jess

-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.