Bug #109943 | ODBC Connector 8.00.32 (32bit/64bit) - no/ wrong umlauts with Access 365 | ||
---|---|---|---|
Submitted: | 6 Feb 8:16 | Modified: | 28 Mar 12:25 |
Reporter: | Klaus Riech | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 8.0.32 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | ODBC, umlauts |
[6 Feb 8:16]
Klaus Riech
[8 Feb 4:01]
Bogdan Degtyariov
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?
[8 Feb 4:02]
Bogdan Degtyariov
MS Access screenshot with umlauts
Attachment: umlaut_access.png (image/png, text), 8.48 KiB.
[10 Feb 11:07]
Klaus Riech
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)
[28 Mar 12:25]
MySQL Verification Team
Hello Klaus Riech, Thank you for the details. We once again tried to reproduce your issue but we couldn't repeat it. If you can provide more information, feel free to add it to this bug. Thanks. Regards, Ashwini Patil