Bug #105503 Access 64-bit crashes frequently using Connector 8.0.27
Submitted: 9 Nov 2021 13:03 Modified: 14 Dec 2021 22:21
Reporter: Richard Schroth Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:8.0.27 OS:Microsoft Windows (10 Pro)
Assigned to: CPU Architecture:x86

[9 Nov 2021 13:03] Richard Schroth
Description:
Even doing very simple things, like viewing a table, Access will frequently crash when working with MySQL data

How to repeat:
Use Access with MySQL data
[9 Nov 2021 13:19] Richard Schroth
I have a small table with about 500 records, and Access will crash reliably when I open the table, sort it by one of the columns, set filter criteria, etc.  Also just opening a second table will crash it.
[9 Nov 2021 13:33] MySQL Verification Team
Thank you for the bug report. Please provide a create table statement and a dump file to populate the table (use the File tab to attach a zip file for) and also the server MySQL version which are you connected to.
[10 Nov 2021 18:44] Richard Schroth
The MySQL server we are connected to is '5.7.36-enterprise-commercial-advanced-log'

The version of Access I am using is Office 365  Microsoft® Access® for Microsoft 365 MSO (Version 2110 Build 16.0.14527.20234) 64-bit

I don't really work that much with MySQL, and I know on the connector there are a lot of different checkboxes that I don't fully understand.  Are there preferred settings for when connecting using Access?

You would be welcome to do a remote session with me to see the problem.

Dick Schroth
President
Schroth Systems Consulting, Inc
www.schrothsystems.com
Cell: (860) 798-0008
Making Computers Work for People
[10 Nov 2021 20:48] MySQL Verification Team
Thank you for the feedback. I was able to repeat and converted the files provided as private.
[24 Nov 2021 23:10] Ronny H.
Windows Event Viewer shows arbitrary errors while using MySQL ODBC 8.0.27

Faulting application name: MSACCESS.EXE, version: 16.0.14527.20276, time stamp: 0x6186ed07
Faulting module name: myodbc8w.dll, version: 8.0.27.0, time stamp: 0x614d5c7a
Exception code: 0xc0000005
Fault offset: 0x000000000006b670
Faulting process id: 0x4fbc
Faulting application start time: 0x01d7e186bb486f8b
Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\Program Files\MySQL\Connector ODBC 8.0\myodbc8w.dll

Faulting application name: MSACCESS.EXE, version: 16.0.14527.20276, time stamp: 0x6186ed07
Faulting module name: VBE7.DLL, version: 0.0.0.0, time stamp: 0x612d2571
Exception code: 0xc0000005
Fault offset: 0x000000000014e4f1
Faulting process id: 0x77f8
Faulting application start time: 0x01d7e186ce4ab388
Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\VBA\VBA7.1\VBE7.DLL

Faulting application name: MSACCESS.EXE, version: 16.0.14527.20276, time stamp: 0x6186ed07
Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6
Exception code: 0xc0000374
Fault offset: 0x00000000000ff199
Faulting process id: 0x76e0
Faulting application start time: 0x01d7e1874625cba5
Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
[26 Nov 2021 11:06] Zoltán Szalai
Also affects me. (MS Office 365 64 bit)
 When I relinked a table to MySQL ODBC driver 8.0.27, the application crashed. After linking back the table to odbc driver 5.3.10, the ID (primary key) field was missing. After linking it again with 5.3.10, the table was ok.

Event log example:
"
A hibát okozó alkalmazás neve: MSACCESS.EXE, verzió: 16.0.13127.21792, időbélyeg: 0x61631a93
A hibát okozó modul neve: myodbc8w.dll, verzió: 8.0.27.0, időbélyeg: 0x614d5c7a
Kivételkód: 0xc0000005
Hiba pozíciója: 0x000000000006b670
A hibát okozó folyamat azonosítója: 0x3484
A hibát okozó alkalmazás indításának időpontja: 0x01d7ca5b18c12d89
A hibát okozó alkalmazás elérési útja: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
A hibát okozó modul elérési útja: C:\Program Files\MySQL\Connector ODBC 8.0\myodbc8w.dll
Jelentés azonosítója: 8fd901ad-95c6-4e0f-b275-dcde6669c1b4
A hibát okozó csomag teljes neve: 
A hibát okozó csomag relatív alkalmazásazonosítója:
[1 Dec 2021 5:50] Bogdan Degtyariov
Posted by developer:
 
The crash is fixed. The patch and the unit test are pushed into the source tree.
[14 Dec 2021 22:21] Philip Olson
Posted by developer:
 
Fixed as of the upcoming MySQL Connector/ODBC 8.0.28 release, and here's the proposed changelog entry from the documentation team:

Microsoft Access could unexpectedly halt when browsing MySQL linked
tables when columns in the tables had gaps; and for roughly 100+ record
tables as the ODBC driver was incorrectly using memory allocating
functions from libmysqlclient.

Thank you for the bug report.
[23 Dec 2021 11:56] Alexander Menk
When will 8.0.28 be released?

Is there a MSI Package of a pre-release?