Bug #23820 Jet Direct error linking any tables or views
Submitted: 31 Oct 2006 23:10 Modified: 28 Nov 2006 21:08
Reporter: Geoff Hart Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:5.0.5 Beta OS:Windows (WinXP SP2)
Assigned to: Peter Harvey CPU Architecture:Any
Tags: Jet, ODBC

[31 Oct 2006 23:10] Geoff Hart 
Description:
Linking any tables or views using the MySQL 5.0.5 Beta driver from Access 2003 results in a Microsoft Jet Error and the tables fail to link. You can connect to the database and get a list of the tables, but when you try to link them the error appears.

MyODBC 5.0.5 Beta
MySQL 5.0.24a-community (locally on PC)
MS Access 2003 (11.6566.6568 SP2)

Exact Error: "The Microsoft Jet database engine could not find the object 'om_a10a11bytepacketcountbypdsn_r30'. Make sure the object name exists and that you spell its name and the path name correctly.

Same setup running MyODBC 3.51.12 works fine.

How to repeat:
Link any table from Access 2003.
[31 Oct 2006 23:10] Geoff Hart 
MDAC Version Report

Attachment: results.xml (text/xml), 5.71 KiB.
[28 Nov 2006 21:08] Jess Balint 
The exact issue reported here is a bug in the way underscores were handled in catalog functions. Fixed in svn rev663 which would be in the 5.00.08 release.