MySQL Manual
9 MySQL APIs
- 9.2 MySQL ODBC Support
- 9.2.1 How To Install MyODBC
- 9.2.2 How to Fill in the Various Fields in the ODBC Administrator Program
- 9.2.3 Connect parameters for MyODBC
- 9.2.4 How to Report Problems with MyODBC
- 9.2.5 Programs Known to Work with MyODBC
- 9.2.6 How to Get the Value of an
AUTO_INCREMENTColumn in ODBC - 9.2.7 Reporting Problems with MyODBC
9.2.7 Reporting Problems with MyODBC
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:
- 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'.
-
Tag the `Trace MyODBC' option flag in the
MyODBCconnect/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 themyodbcd.dlldriver (see the item above). - 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.
You should also try duplicating the queries in the mysql monitor
or admndemo to find out if the error is MyODBC or MySQL.
If you find out something is wrong, please only send the relevant rows (max 40 rows) to myodbc@lists.mysql.com. Please never send the whole MyODBC or ODBC log file!
If you are unable to find out what's wrong, the last option is to make an archive (tar or zip) that contains a MyODBC trace file, the ODBC log file, and a README file that explains the problem. You can send this to ftp://support.mysql.com/pub/mysql/secret/. Only we at MySQL AB will have access to the files you upload, and we will be very discrete with the data!
If you can create a program that also shows this problem, please upload this too!
If the program works with some other SQL server, you should make an ODBC log file where you do exactly the same thing in the other SQL server.
Remember that the more information you can supply to us, the more likely it is that we can fix the problem!
