ADO msdasql.dll access violation after mysql upgrade

From: Richard Ireland (richard_at_diversitech.net)
Date: 10/28/03 

Date: Tue, 28 Oct 2003 19:27:05 +0800

We recently upgraded to MySQL4.0 (Due to a bug in MySQL 3.23 which was
causing the mysqld to crash on the server with a certain query). All
our existing databases and apps, some in Java, some in PHP, some in
Perl, some in Kylix1, some in Kylix 3 work fine with the new server.

However, on one w2k workstation, all the apps created in Delphi7 crash
when connectiong to mysql with the following AV....

Access violation at address 1F6B9339 in module 'msdasql.dll'. Read of
address 687F4584

I am using MyODBC driver 3.51.03. msdasql.dll version 2.53.6200.0.

I tried updating MDAC to 2.8 -- it's fails and "Rolls-back"
automatically. But I guess the Roll-back didn't work, cause after
doing this nothing relating to ADO would work (not even ODBC Manager
-- irrespective of MySQL). I tried MDAC2.7, 2.6, 2.5 too. In the end
the only way I could get stuff working again was a reinstall of
Windows2000. I read that W2K SP1 and above upgrades MDAC too. I've
installed upto SP4, and all the critical updates.

The Delphi7 crash is very perculiar in the IDE....
   a) I can connect to the MySQL database with an ADOConnection.
   b) As soon as I activate a TADOQuery to connect to it (either
run-time or design-time), the AV occurs.
   c) Then clicking on any "non-windowed" component in the IDE
[design-time] (even not DB related, like a TTimer) causes Delphi to
crash (with no message). Clicking on other controls (like TButton,
TPanel, TDBGrid) doesn't crash it.

The problems do not occur on a workstation running Delphi7 under
WinXP.

Any suggestions will be much appreciated!

Quantcast