| Bug #65250 | MS Access crashes with MySQL 5.1 ODBC Connector on Windows Server 2008 R2 (x64) | ||
|---|---|---|---|
| Submitted: | 9 May 2012 5:45 | Modified: | 22 Jun 2012 10:28 |
| Reporter: | Marc Meessen | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S2 (Serious) |
| Version: | mysql-connector-odbc-5.1.11-win32 | OS: | Windows (Server 2008 R2 (x64)) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | crash, MSAccess, ODBC, refreshlink | ||
[9 May 2012 13:50]
MySQL Verification Team
Thank you for the bug report. Please check for duplicate: http://bugs.mysql.com/bug.php?id=65200. Thanks.
[10 Jun 2012 1:00]
Bugs System
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".
[20 Jun 2012 20:03]
alex barcza
I'm having same issue. Had to go back to 5.1.10 to stop crashes
[22 Jun 2012 10:28]
Bogdan Degtyariov
This is a duplicate of bug 65200, which has recently received the patch.
Description: Within an MS Accesss application running on a Windows Server 2008 R2 (x64), refreshing the link to tables on a MySQL Server causes the msaccess.exe to crash if the ODBC driver is version 5.1.11 (32bit). The Server is used as a terminal server in user mode. On the same server using the ODBC Connector 5.1.5 (32bit), refreshing the link works fine. How to repeat: 1. Within msaccess link a table (i.e. Table_1) through MySQL ODBC connector (originally in this application it was linked through a 3.51 connector) 2. Write a VBA code within the application, that refreshes this link, like this: db.TableDefs("Table_1").Connect = "DATABASE=DB01;DSN=DBDSN;OPTION=18475;SERVER=Stunden;UID=user;PWD=pass;" db.TableDefs("Table_1").RefreshLink If the ODBC Connector is 5.1.11 the msaccess.exe crashes, if the connector is 5.1.5, the link gets refreshed without any problem. On a Windows 7 x64 system with ODBC Connector 5.1.6, refreshing the link works without a problem, too. Suggested fix: As a workaround, use ODBC connector 3.51.25, 5.1.5 or 5.1.6 (I tested those 3, since I had them at hand).