MySQL Bugs: #109943: ODBC Connector 8.00.32 (32bit/64bit)

Bug #109943	ODBC Connector 8.00.32 (32bit/64bit) - no/ wrong umlauts with Access 365
Submitted:	6 Feb 8:16	Modified:	10 Feb 11:13
Reporter:	Klaus Riech	Email Updates:
Status:	Analyzing	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	8.0.32	OS:	Windows
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	ODBC, umlauts

Description:
When entering (insert/update) umlauts (ä,ö,ü) in our Access Frontend they are not properly translated. For example the name "Müller" shows up as "MÃ¼ller".

We use a MS Access 365 frontend with linked tables to a MySQL backend.
Tested with MySQL Version 5.7.41 and 8.0.32.

This works fine with ODBC connector 8.0.29.

Reproduced with the ODBC 32 bit as well as the 64 bit version.

How to repeat:
Windows 10
In MS ACCESS 365 create a link to a MySQL table wit a text field (VarChar, Text,..)
Create a form linked to that table as recordsource.
Enter a text with Umlauts (insert) like "Müller" or change an existing text field (update).

Suggested fix:
Um? Just fix it?
We went back to version 8.0.29 but now we are dealing again with the "date overflow" bug. (Bug #107235)

Unfortunately, I was not able to repeat the issue with the default settings.
Please check the attached screenshot (umlaut_access.png).

However, there still can be a problem if you use additional ODBC connection options. Do you use NO_SSPS=1 (Prepare statements on the client in GUI)?

Are you using the ANSI or UNICODE version of the ODBC driver?

MS Access screenshot with umlauts

Attachment: umlaut_access.png (image/png, text), 8.48 KiB.

We use the UNICODE version of the ODBC driver.
The "Prepare statements on the client" option is deactivated.

The precise Access Version we use is:
Microsoft 365 Apps for Enterprise.
Version 2301 (Build 16026.20146 Click-and-go)