MySQL Bugs: #11698: Every attempt to update or add linked odbc tables crashes Access

Bug #11698	Every attempt to update or add linked odbc tables crashes Access
Submitted:	2 Jul 2005 2:21	Modified:	8 Oct 2007 9:28
Reporter:	JOHN BISSELL	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	3.51.11-2	OS:	Windows (Windows 2000 Sp4)
Assigned to:		CPU Architecture:	Any
Tags:	ODBC5-RC

Description:
Windows 2000, Office XP Developer,Access XP, odbc-connector 3.51.11-2) - after installing the "Update Rollup 1 for Windows 2000 Service Pack 4 (KB891861)" every attempt to update or add linked odbc tables crashes Access (using the existing data link seemed fine). They updated msjet40.dll (7/19/2004), and it seems to not play well with the odbc program. Replacing the dll with the previous version (3/1/2004) fixed the problem.

How to repeat:
Open an Access database, file, get external data, link tables. Select Files of Type = ODBC Databases, using machine data source, I selected my ODBC source that was previously configured, then click OK, there is about a 10 second pause, then Access crashes (get the MS submit problem pop-up).

Alternatively, you can right click on an existing linked odbc table, select Linked Table Manager, then select one or all of your tables to update and click OK, there is about a 10 second pause, then Access crashes (get the MS submit problem pop-up).

Suggested fix:
Workaround is to replace the newer msjet40.dll (file date 7/19/2004) with the previous version (file date 3/1/2004).

I have installed SP4 on Windows 2000. But I was not able to repeat your bug. Could you please say me more information about this crash (table deffinition and so on)?

I have the same bugs with all my computers.
W2K SP4

MDAC 2.8 SP1
http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-a9e0-3a1afbd59...

Jet 4.0 SP8
http://www.microsoft.com/downloads/details.aspx?FamilyID=2deddec4-350e-4cd0-a12a-d7f70a153...

When I retrogade to Myodbc 3.51-06, all is working again !

I have the same bugs with all my computers.

Config my computers:
W2K SP4 with Update Rollup 1 for Windows 2000 Service Pack 4 (KB891861), MDAC 2.8 SP1, JET 4.0 SP8,
Myodbc 3.51-06 or 08.

When I uninstall the "Update Rollup 1 for Windows 2000 Service Pack 4 (KB891861)", all is working again!

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".

I files some kind of document this morning -- it complied as best possible with the writeup for MySQL ODBC. The e-mail address was tooheys@fullchannel.net

In any case, the issue I am filing about is a great deal like the one described here.

My submittal has the address of the MySQL database, the Access database, the ODBC filing -- hopefully the whole nine yards.

Based on other comments, I regressed my MySQL ODBC from MyODBC-3.51.11-2-win back to MyODBC-3.51.06.

Same exact results (MS bug catcher).

When I ran this test the trace was on -- if anyone wants the new trace please let me know.

I have the same bug. Where can we find the previous version (3/1/2004) of msjet40.dll, and how can we update it?

I can  not recreate the problem here but I am using/have a slightly different mix of software here. We need an ODBC trace so we can see what is going on leading up to the crash.

It would help if people were using the just completed 3.51.12 release to do the trace. It can be found at; ftp://ftp.mysql.com/pub/mysql/hidden/connectors/odbc and should be published to the regular download area soon.

Updated to 3.51.12, but still doesn't solve problem.

I have exactly the same problem on all windows 2000 computers whith same configuration described above.  JEt4 sp8 , win2000 sp4. I tried to downgrade myodbc without results. As well, i can't connect to the database through VB6. I create a new connection, i find tables but when i click on test connexion button i have got an error message something like that (i try to transate from french!!!) "connexion test failed,error during provider initialisation" 

Thank you for your help

Good morning.
I just noticed -- this bug has a "non-critical" rating -- boulderdash when anyone is in the middle of this one it becomes all consuming primarily because it is an issue where Microsoft and MySql are not playing nice together. Generally this is not the case but this one hurts.

Last summer, I finally replaced MSJET40.DLL with a newer version. I recall leaving a ton of documentation around so I could intelligently comment about this if asked.
It is all gone. I also recall that sometime in the fall, Microsoft issued an upgrade for MSJET40.DLL -- I probably wiped out the documentation at that time.

At this point, I can not give you specifics but if you are experiencing this problem then most likely WINNT\SYSTEM32\MSJET40.dll is most likely causing it. I suggest replacing it. First, check Microsofts knowledgebase. If that is not fruitful check your own system. When I did the original replace, I used a version of MSJET40.dll that was on my system.

Good Luck -- just remember this is the issue de jour -- when this one is fixed someone will find an new one.

I have the same problem>  I posted this comment on bug# 12238 and I applogize for duplicating it here. 
This is kind of critical!
[23 Feb 22:51] Paul Therrien I have Server 1: Windows 2003, MySql Server 5.0.
I have Server 2: Windows 2000, MyODBC drive 3.51, MS Access 2003.
On Windows 2000 I am running MS Access, whenever I try to link tables to My ODBC
Access crashes.
I select the MyODBC data machine source and click OK. Within 3 seconds I get a
"Microsoft Office Access has encountered a problem ...." window.  I send the
error report and Access restarts and asks me to save the database as a backup
version.

Any clues?, anybody?

Paul 
therrien@cox.net

Paul,
What I did as a work-around was install the previous version of msjet40.dll (dated 3/1/2004). The version of this file that came in the Windows 2000 UpdateRollupPackage (critical updates) is dated 7/19/2004. You can get the file out of the uninstall folder created by the update, just do a search for that file name. That fixed mine, I hope it fixes yours!

John Bissell

In looking at Microsofts postings it seems like the release of JET4.09025.0 should not have been extend to Windows 2000.  I believe you are correct and we need JET 4.0.8015.0 
see: http://support.microsoft.com/kb/239114/#XSLTH3120121123120121120120
They don't state it specifically, but the following excerpt is suspicious:
<quote>
If you are running Windows 2000 Service Pack 4 Update Rollup 1, you have a later version of Jet 4.0 than the version that is included with Jet 4.0 SP 8. We recommend that you install the latest service pack for Windows 2000. For more informationinformation about how to obtain the latest service pack for Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base: 
260910 (http://support.microsoft.com/kb/260910/) How to obtain the latest Windows 2000 service pack 
If you cannot install Windows 2000 Service Pack 4 Update Rollup 1, you can use Windows2000-KB829558-x86-ENU.exe to install Jet 4.0 Service Pack 8 on computers that are running Windows 2000. Click the following link to download and to install the correct version of Jet 4.0 Service Pack 8 on computers that are based on the language version of Windows 2000 that is running on the computer.
</quote>

John,

Please, explain clearly, is problem solved by the installation of "proper" version of msjet40.dll? If no, have you tried to use newer versions of MyODBC?

Valeriy, 

We ended up installing msjet40.dll version 4.0.7328.0.
We are using MyODBC version 3.51.12. 
This seems to handle the issue.
 
(Note: We wanted to install msjet40.dll version 4.0.8015.0, but for various reasons were unable to get a copy of it and settled on 4.0.7328.0 when we found our problem resolved.)

Paul 

Paul J. Therrien
Andeco Software, LLC
18424 Lakehaven Ct
Baton Rouge, LA 70817
225-756-4480

Good Morning -- this one seems to not want to go away.

I think Paul Therrien's [24 Feb 0:59] comments are a bit of tea leaf reading and probably are very insightful. This is the most complete discription of the issus that I've seen -- good thinking Paul.

I did root around and found a JET 4.0.8015.0 version of MsJet40.DLL. I'm going to put it in a zip file with a big sign to not delete.

If anyone wants a copy, please contact me at Tooheys@FullChannel.net. I'll forward the zip file to you.

(I hope this posting does not violate someones rules. If there is a better way to accomplish this please let me know.)

Best to all

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".

Has this been fixed? So that 3.51.12 works with the latest Jet dll?

It definatly does not work.

Running access 2003 SP2 on a Windows 2003 server R2
MYSQL ODBC 3.51.12 
MSJET40.dll version 4.09025.0
It immediatly crashes when I want to link or add a table through ODBC-driver.

Help required

It looks like this has been fixed, under windows 2000, using MSJet 4.0.9025 and MySQL ODBC v3.51.20!

Thanks Gavin for your report.

All reporters,

please try it again with the new version. We will be glad to hear your feedback.

Susanne

This bug was originally found using Windows 2000. These comments are for Windows XP, Tommorrow is my 70th birthday and I am hopeful to never have to return to VISTA -- ugh!

In all cases one system has Access 2007 using MsJet40 sub-version 8618 with MySQL ODBC 3.5.11; the other system has Access 2003 wuing MsJet40 sub-version 8015 with the same MySQL ODBC.

In all cases this is working -- in other words the issue with W2K did not migrate to XP or its siblings.

Best to all

This bug was originally found using Windows 2000. These comments are for Windows XP, Tommorrow is my 70th birthday and I am hopeful to never have to return to VISTA -- ugh!

In all cases one system has Access 2007 using MsJet40 sub-version 8618 with MySQL ODBC 3.5.11; the other system has Access 2003 wuing MsJet40 sub-version 8015 with the same MySQL ODBC.

In all cases this is working -- in other words the issue with W2K did not migrate to XP or its siblings.

Best to all

Hi Frank,

Wow! 70 years. Happy Birthday.
I'll hope, that you will have lots of further healthy years.

Don't get angry about Vista. Because that only occurs, that your hair will get gray much faster and your skin get more crinkles. :)

It's really nice to read, that we have users of your age, that are interested in our product.

I'll hope, you enjoy MySQL further on.

Regards,

Susanne

Suzanne, thank you -- I think I was feeling a little old when I wrote that.

MySQL is a great product. Its a great product because it delivers functionality and it works. This allows folks like me to translate that product into something that works for our various communities. Therefore we all benefit.

I know this sounds preachy, but there is nothing more thrilling than a User who has solved one of their problems with software we developed and they do not know nor do they care how it happened. Really cool.