MySQL Bugs: #15277: Windows 2000 SP4 with Access can't link new MySQL connected tables

Bug #15277	Windows 2000 SP4 with Access can't link new MySQL connected tables
Submitted:	27 Nov 2005 21:30	Modified:	19 Mar 2007 10:36
Reporter:	Uwe Pfeiffer	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	3.51	OS:	Windows (Windows 2000 SP 4)
Assigned to:		CPU Architecture:	Any

Description:
This is a hint for all users which have the same following problem :

After installation from Windows 2000 SP 4  Microsoft Access is no longer able to connect to a new MYSQL-table using  the normal dialog for connected ODBC-tables.

The command TransDatabase acLink will do nothing. You don't get any error message.
Existing connections work fine.

For details see
http://forums.mysql.com/read.php?65,38431,53138#msg-53138

After deinstallation from SP4 the problem was solved.

How to repeat:
Install SP 4 on Windows 2000

Suggested fix:
http://forums.mysql.com/read.php?65,38431,53138#msg-53138

Deinstall Windows SP 4  !!!

I was not able to reproduce the bug on 3.51.12. Could you please upgrade myodbc driver ?

It's easy to reproduce the bug. You just need latest msjet40.dll file ( 4.0.9025.0 ) !!! This file comes with W2K SP4 !!!

to Marcin Lizer:
Could you please advise me where I can download msjet40.dll file (4.0.9025.0 ) for windows 2003 ?

How do we make this a critical Severity:??
Not being able to change tables without replacing the current version of msjet40.dll 4.0.9025.0 with version 4.0.8618.0 is "critical".

This change was issued as a security patch. 
So the concept of rolling back to a less secure version rates "critical".

I have several other ODBC drivers and they all still work, only myOdbc fails miserably.

Vasily Kishkin, did you get a copy of the msjet40.dll's you where looking for?
An up to date 2003 server will have it installed. 
If you need one or an old one, contact me via email.

Is anything being done with this bug? It is still an issue even with the .12 release of the connector. What other information is needed so we can get this fixed?

I running the following:  Windows 2000 SP4 w/ Access 2003 and the latest version of MySQL.  

Each time I try to link to the database tables through the wizard, Access crashes.  However I have no problem generating ADO recordsets through VBA?

Any solution or suggestions to fix this problem?

This is an urgent issue for our company.

Thanks in advance.

John

mySQL driver is currently FUBAR.
I have many other 3rd party ODBC drivrs ond only the mySQL driver FAILS.

For win 2000 SP4
Do a search in the windows system32 for "msjet40.dll".
Find a copy of version 4.0.4431.3 (will be in a backup from a SP)
KEEP a copy of msjet40.dll version 4.0.4431.3 in a safe place so you do not loose it.
COPY the msjet40.dll version 4.0.4431.3 to system32\dllcache\ folder
NOTE this is a hidden folder.
RENAME the system32\msjet40.dll to something else.
you can delete it after the next reboot.
COPY  the msjet40.dll version 4.0.4431.3 to system32 folder.
This will last untill the next MS update occoures.

SHAME on mySQL for calling this a S3 (Non-critical) problem.

I have heard so much about mySQL, i am a die hard MS/Access/SQL Server/VB type of guy, just installed a mySQL based support app, went to use ODBC to get some under the hood reports using Access - Died as per this bug - To say non-critical is not a fair statement - i am now stuffed and looking for alternatives.
Note. I have a fair few datasources to connect to and don't like the idea of having to rollback dll's just to satisfy one instance, looking at the web/forums etc this bug has been out long enough for an urgent patch to be issued, found a 351.12-2 windows install - still no change.
Is there a windows patched install or even an ETA yet?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

[15 Jan 1:00] Bugs System No feedback was provided for this bug for over a month, so it is being suspended automatically.
?????
[11 Jan 0:49] Neil Grover 
[9 Jan 23:33] Paul Dragon
[9 Jan 22:52] John Lewis
[4 Jan 15:52] Bryan Buschmann
[18 Dec 2005 21:50] Paul Dragon

Did I miss something, where is Vasily Kishkin and why does he not respond to our postings?

Hi  to all reporters.
This is not a MySQL bug. Proof is that if you rollback jet dll, everything works *and* " [9 Jan 22:52] John Lewis: However I have no problem generating ADO recordsets through VBA" which I can confirm.
We do not have specs for MS software and we are completely unable to do anything about it but to wait for MS to fix it. 
As for severity it could only be set to S2 or S3 since workaround is available.
We can all hope that one day MS will release *any* piece of SW which will not be followed by gigantic service pack...

Tonci Grgin is clueless as a software developer.
"This is not a MySQL bug. Proof is that if you rollback jet dll, everything works"

The problem is ONLY when adding tables to Access-whatever. After they are added, editing the data is not the issue.

If all other drivers connect to with the new dll except mySQL, guess where the problem lays? The problem lays in the closed mental mindset of those who wish not to fix a problem. It is with those who wish to point fingers. FUBAR

In 30 years of software development and management, it maters not who thinks who is in error. What maters is who steps up to the plate and FIXES the problem.

This is where the Total Cost of Ownership needs to be considered when choosing software. I certainly am considering switching back to msSQL. I was considering purchasing a mySQL support package.

http://support.microsoft.com/kb/239114 provides version history for MSJet.

Paul Dragon's solution works but you don't necessarily have to go as far back as version 4.0.4431.3 - I went back to 4.0.7328.0 and that worked.

Cheers,

Tim.
http://www.pwp1.com

This needs to be re-verified with the latest 3.51 release, and possibly the latest JET release. If it's a Microsoft problem, we need to report it to them and add the details of how it has been reported here.

Hi all.

I am unable to repeat reported behavior using:
 - MySQL 5.0.38BK on WinXP Pro SP2 localhost
 - MyODBC 3.51.14
 - Jet engine version 4.0.8618.0
 - MS Access 2003, 11.6566.8122, SP2

This is just my opinion. It is not my intention to fully explain the entire problem nor it's supposed to be fully correct. I just happen to come across this report while cleaning my inbox.

From what I see, Edin was right in 
http://forums.mysql.com/read.php?65,38431,53138#msg-53138 although he didn't know why... By creating 1 Access table in database he got tables Access requests no matter to which server it's connected(!). Anyone looking at ODBC traces should have been able to see things like
|   |   |   |   [ERROR][set_stmt_error][.\error.c][200]message: Table 'test.msysconf' doesn't exist
Of course it doesn't exists anywhere but in MS products! This shows that Access is *not* checking the server type ODBC DSN points to but rather assumes it's MS product. This brings us to, whether Paul likes it or not, inability to change / check anything in poorly documented internals of closed source applications... By checking logs / traces, which is most tiresome work that none of reporters did, our developers had to *work around* what is still MS bug in my opinion.