Bug #17681 MS Access and Linked tables. MyODBC 3.51.12
Submitted: 23 Feb 2006 22:16 Modified: 24 Feb 2006 1:14
Reporter: Paul Therrien Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:MySQL Server 5.0 OS:Windows (Windows 2000)
Assigned to: MySQL Verification Team CPU Architecture:Any

[23 Feb 2006 22:16] Paul Therrien 
Description:
I am posting this as a new bug, but have added this as a comment to 2 other bugs.  I appologize if this causes confusion or more work, but this is a serious issue and not a non-critical one as bug # 12238 states.
------------------------------------------------
I have Server 1: Windows 2003, MySql Server 5.0.
I have Server 2: Windows 2000, MyODBC drive 3.51.12-2, MS Access 2003.
On Windows 2000 (server 2), I am running MS Access, whenever I try to link tables to MyOdbc connection to Mysql 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.

In addition I am able to go to Ms Excel and open a database query into this ODBC datasource w/o trouble. 

Any clues?, anybody?

Paul 
therrien@cox.net

How to repeat:
I don't know how to tell one to report this.  As an example; on another workstation I have MYSQL 5.0 and MyODBC 3.51.12 and MS Access 2002 on Windows XP and everything is fine.
[23 Feb 2006 22:46] Paul Therrien 
I have found the following message in SQL.LOG from ODBC Trace routine:

DIAG [S0002] [MySQL][ODBC 3.51 Driver][mysqld-5.0.17-nt]Table 'goeletweb.msysconf' doesn't exist (1146)

Checking on this now!
[23 Feb 2006 23:04] Paul Therrien 
It appears that MS Access is expecting to find a database table in the SQL database called msysconfig.
I refer you to this link:

http://office.microsoft.com/en-ca/assistance/HP051876211033.aspx

Its expecting the table to have three records in it as well.
This supposedly an optional file, but that doesn't appear to be the case.
[24 Feb 2006 1:14] MySQL Verification Team 
I was unable to repeat the behavior reported and most probably this
issue is related in some upgrade issue on your OS environment I suggest
you to compare the MSjet40.dll versão between the machine where it
works with the one you have on the environment offended.