MySQL Bugs: #37010: mysql-connector-odbc-5.1.4 takes down Access 2003

Bug #37010	mysql-connector-odbc-5.1.4 takes down Access 2003
Submitted:	27 May 2008 15:32	Modified:	29 May 2013 6:13
Reporter:	Adam Smith	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	05.01.0004	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any

Description:
Access 2003 crashes when trying to link to MySQL data sources.

It happens with existing Access 2003 files that used to work with the mySQL Connector 3.51.

A reproduction case starting from scratch is provided.

How to repeat:
1. download mysql-connector-odbc-5.1.4-win32.msi
2. use Control Panel / Administrative Tools / Data Sources to create a new MySQL System DSN

3. launch Access 2003
4. create a new blank database
5. go to the Tables section and right click
6. choose Linked Tables...
7. select ODBC from the dropdown
8. pick the Machine Data Source created in step 2
9. select a table and click OK
10. linked table appears
11. double click to open linked table
12. Boom! Please tell Microsoft about this problem

Hi Adam and thanks for your report. This is actually a duplicate of Bug#36731 but as I got no feed back from Egor there I will not close your report. We have seen some troubles with Access/5.1.4 combination described in Bug#36203 but nothing similar to this.

So please see what I asked from Egor and notify me of your results.

I tried using Excel 2003 rather than Access 2003 to read from my MySQL database.  Both crash in the same memory location (see below).  The query performed in Excel is very simple (see below).

Mysql server is version 5.0.24a-standard and is hosted via dreamhost.com in LA.  The Microsoft Query version stamp is 11.0.5510.0.

Event	Application Failure
Bucket ID	Not Available
Bucket Table	Not Available
Application	msaccess.exe
Application Version	11.0.6566.0
Application Stamp	42cdb33e
Module	myodbc5.dll
Module Version	5.1.4.0
Module Stamp	4804d66e
Debug	0
Offset	00017f97
Date	6/2/2008 12:53:14 AM
	
Event	Application Failure
Bucket ID	Not Available
Bucket Table	Not Available
Application	excel.exe
Application Version	11.0.8211.0
Application Stamp	47dcb10b
Module	myodbc5.dll
Module Version	5.1.4.0
Module Stamp	4804d66e
Debug	0
Offset	00017f97
Date	6/2/2008 1:00:50 AM

myodbc.sql log file:
===========

-- Query logging
--
--  Driver name: MySQL ODBC 5.1 Driver  Version: 05.01.0004
-- Timestamp: 080602  1:21:06

SHOW TABLE STATUS FROM `film_depot_test` ;
SHOW TABLE STATUS LIKE 'boolean_type';
SHOW TABLE STATUS LIKE 'run_type';
SHOW TABLE STATUS FROM `film_depot_test` LIKE 'run\\_type';
SHOW COLUMNS FROM `film_depot_test`.`run_type`;
SELECT `run_type_id`,`run_type_name` FROM `film_depot_test`.`run_type` LIMIT 0;
SHOW COLUMNS FROM `film_depot_test`.`run_type`;
SELECT `run_type_id`,`run_type_name` FROM `film_depot_test`.`run_type` LIMIT 0;
SELECT run_type_0.run_type_id, run_type_0.run_type_name, run_type_0.run_type_id

FROM film_depot_test.run_type run_type_0;

Hi Adam.

I did not noticed any problems like described both with Access and with Excel2003...

I presumed maybe the problem was with "_" in both database and table names so I made little test:
Server version: 5.0.60-pb1096-log MySQL Pushbuild Edition, build 1096
CREATE DATABASE bug_37010;
USE bug_37010;
CREATE TABLE `run_type`(`run_type_id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY, `run_type_name` VARCHAR(50));

Now, Access produced following log:
080602 12:37:10	      7 Connect     root@localhost on bug_37010
		      7 Query       SET NAMES utf8
		      7 Query       SET character_set_results = NULL
		      7 Query       SELECT Config, nValue FROM MSysConf
		      7 Query       SHOW TABLE STATUS
080602 12:37:12	      7 Field List  run_type 
		      7 Query       SHOW TABLE STATUS LIKE 'run\\_type'
		      7 Field List  run_type 
		      7 Query       SHOW KEYS FROM `run_type`
080602 12:37:13	      7 Query       SELECT `run_type`.`run_type_id` FROM `run_type`
080602 12:37:17	      7 Quit   

and Excel:
080602 12:40:25	     12 Connect     root@localhost on 
		     12 Query       SET NAMES utf8
		     12 Query       SET character_set_results = NULL
		     12 Query       SET SQL_AUTO_IS_NULL = 0
		     12 Query       show databases like '%'
		     12 Quit       
080602 12:40:35	     13 Connect     root@localhost on bug_37010
		     13 Query       SET NAMES utf8
		     13 Query       SET character_set_results = NULL
		     13 Query       SELECT run_type_0.run_type_id, run_type_0.run_type_name
FROM bug_37010.run_type run_type_0
ORDER BY run_type_0.run_type_id
		     13 Quit       

Both correctly displayed the table in question (Excel of course added "0", run_type_0.run_type_id	run_type_0.run_type_name).

Are you by any chance using SS PS emulation or something that is known not to work as expected (BIGINT or something)?

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'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.