Bug #11288 Access 2003 crashes when creating an ODBC link to a MySQL table
Submitted: 13 Jun 2005 14:05 Modified: 15 Jun 2005 7:32
Reporter: Erik Uffelen Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:ODBC 3.51 11-1 OS:W2003 SP1
Assigned to: CPU Architecture:Any

[13 Jun 2005 14:05] Erik Uffelen
Description:
A few days ago i migrated my SQL server to a new Windows 2003 server. This server, newly installed with service pack 1.

All the latest software is used (MySQL 4.1.11 and MyODBC 3.51 11.1)

When I use my access databases the already existing links work fine. But when I try to create new links access crashes. Also using linked table manager and refreshing old links crashes access.

Also see the thread on the MySQL forum:
http://forums.mysql.com/read.php?37,23875,29267#msg-29267

The supposed resolution is uninstalling SP1. this is really not an option because this would go against company policies and would leave the server vunrable to security threats.

I am not sure if the problem lies with the JET enginge implementation of w2k3 SP1 (4.0.9025.0) or the ODBC implementation of MySQL

How to repeat:
On W2003 sp1 (with latest MS jet engine)

Create an ODBC (user/system) link to a MySQL database (3 or 4 doesnt matter, i have both running on different servers (version 3 on w2K and version 4 on W2k3)

Open access 2003
Make a linked table from the just created odbc resource.. when the existing tables in the selected database should be displayed...

Access crashes.... every time

Suggested fix:
? either the JET engine should be fixed or the ODBC driver should be fixed.
[13 Jun 2005 23:43] premax -
Have the same problem. I think it is a ms jet issue, not myodbc. Had to uninstall sp1 today :-/
[15 Jun 2005 7:32] Vasily Kishkin
Sorry, As far as I can understand this bug is #9932. The status of that bug is in progress. I hope this error will be fixed soon.
[1 Jul 2005 10:33] Erik Uffelen
FOUD WORKAROUND!:
see: http://www.techspot.com/tweaks/wfp/wfp3.shtml
And it works for me

Essence is to replace ONLY the MSJET40.DLL file with an older verion.

Windows System File protection protects the msjet40.dll file when you try to replace it with an older version. How to fix this issue:

1. Disable system file protection (not verry neat) or...
2. Make sure systemfile protection uses the old MSJET40.dll file

option 2 is preferable to me.  I'll explain how:
1.  Go to %SystemRoot%\system32\dllcache (it is a hidden system folder) and replace MSJET40.dll with the old version (4.0.8618.0)
2. Go to %SystemRoot%\system32 and also replace the MSJET40.dll file.

This must be done in the specified order.
Now SFP thinks the file is correct and will not replace it.

Access works again! Happy days are there again.