MySQL Bugs: #8607: Extended ODBC table refresh in MS Access

Bug #8607	Extended ODBC table refresh in MS Access
Submitted:	18 Feb 2005 19:28	Modified:	18 Feb 2005 20:55
Reporter:	Michael DeLawter	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.11	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any

Description:
When distributing a MS Access front end utilizing linked tables via MySQL ODBC, the tables can take at least a minute before they populate with data and allow the form to open.  This behavior is eliminated by downgrading the ODBC driver to 3.51.10

How to repeat:
Use MySql 4.1.8
MySql ODBC 3.51.11
MS Access 2003

Link MySql tables to a MS Access database, create a form based upon tables.  Distribute the MS Access to another computer and attempt to open the database

edited synopsis

I wasn't able to repeat the behavior reported tranprorting the
Access DB from XP to Windows 2003 Server.

However I guess that behavior is how Access manipulates
the linked tables taking the information from the connect string
which is saved originally in the MSysObjects. My advice for you
is to do code for to link the tables in its first start-up and in this
way it will be save the string connection according how was created
the DSN for example if you changed the user and password this can
be the reason for.

I have already attempted to add code to re-link the tables at the time the front end DB is launched.  This solution did not speed up the performance of the database.  Performance could only be enhanced by installing the down level ODBC driver.  Could the fact that you moved from XP to 2003 server instead of XP to XP have played into the fact that you could not duplicate the slow down?

I can't say you if the XP -> Win 2003 is the difference here,
but maybe another environment factor, for example are
you verified the MDAC version in both machines ?

Yes, both computers that have been used as test beds have MDAC 2.8 SP1 as well as the development computer (running MySql 4.1.8 XP Pro SP2 and developing Access front end all on this computer).  All computers are using Jet 4.0.  Both test computers are new running XP Pro SP2 and the MS Access Runtime version.  The only changes that has made any difference is using MyODBC 3.15.10 instead of 11.  The only other version of MyODBC I have are 7 and earlier which do not work with MySQL 4.1.8 so I have not been able to test any other versions of the ODBC driver.