MyODBC 2.50

This ODBC Driver is provided by MySQL.
The driver is contained in the file MYODBC.DLL.

Coding

Include "Driver={mySQL}" in the connection string to use this driver.

Description

This is an archived version of the MyODBC. Consider switching to 3.51 or 5.1 versions of MyODBC (aka Connector/ODBC).

  If you encounter difficulties with MyODBC, you should start by making a log file from the ODBC manager (the log you get when requesting logs from ODBCADMIN) and a MyODBC log.

  To get a MyODBC log, you need to do the following:

  1.Ensure that you are using myodbcd.dll and not myodbc.dll. The easiest way to do this is to get myodbcd.dll from the MyODBC distribution and copy it over the myodbc.dll, which is probably in your C:\windows\system32 or C:\winnt\system32 directory. Note that you probably want to restore the old myodbc.dll file when you have finished testing, as this is a lot faster than myodbcd.dll.

  2.Tag the `Trace MyODBC' option flag in the MyODBC connect/configure screen The log will be written to file `C:\myodbc.log'. If the trace option is not remembered when you are going back to the above screen, it means that you are not using the myodbcd.dll driver (see above).

  3.Start your application and try to get it to fail.

  Check the MyODBC trace file, to find out what could be wrong. You should be able to find out the issued queries by searching after the string > mysql_real_query in the `myodbc.log' file.

Download

ODBC Driver (MyODBC 2.50) can be downloaded here.

Connection Strings

The MyODBC 2.50 driver can be used to connect to the following data sources:

MySQL

To see available connection options, navigate to the connection strings reference by the above links.

Not the right library?

Try search the kb articles, Q&A content and every connection string here.

Or go to the Q&A forums where you can ask questions.

Browse every article in the knowledge base - | | | - Start over in the connection string reference!

Providers

Articlesread all »