[German]Brief information for the readership and at the same time the question if someone is already affected. I received a user message that Microsoft Access suddenly had problems with SQL database access. All databases suddenly showed the value '#DELETED' in the tables. The problem is the Microsoft SQL Server ODBC driver (shipped with Windows), which seems to go on strike after Office updates.
ODBC access to SQL server is faulty
German blog reader Axel H. contacted me by mail on Saturday, May 28, 2022 to report a specific observation in the Microsoft Access environment related to accesses to a Microsoft SQL server. Axel wrote (translated):
enclosed is a note from me. I was called today by a colleague whose Microsoft Access suddenly did not want to work properly with the SQL Server work properly anymore.
All ODBC tables included in Microsoft Access show only '#DELETED' as content.
After some searching, I found out that it was the 'original' Microsoft SQL Server ODBC driver, the one that comes with Windows.
Sounds bad, a manual fix is required.
New ODBC driver versions work
Microsoft ODBC Driver for SQL Server is a single dynamic-link library (DLL) that provides runtime support for applications that use native code APIs to connect to SQL Server. Microsoft ODBC Driver 18 for SQL Server should be used to create new applications or enhance existing applications that use the newer SQL Server features.
The current version 18.104.22.168 dated February 15, 2022 is offered for SQL Server 2022 Preview here, on Github there is this overview about different driver versions. After some testing, Axel was able to determine that newer versions of the ODBC driver such as v13 and v17 do not show the problem when accessing the databases.
Trouble on the way, Office rollback helps
Axel wrote, that the version, supplied by Windows, is used however surely to >90%, in the field – since Windows brings it along (see here for instance) and does not have to be installed extra. So there could be a lot of trouble within the next days. Axel told me, that Microsoft Office Professional Plus 2019 C2R 32-bit, version 2205 build 16.0.15225.20028 dated 2022-05-24, was affected in his environment (no idea, whether other Office versions are affected). After he did a rollback of Microsoft Office to version 16.0.15128.20248 from 2022-05-17, everything worked again immediately.
Axel concludes that the problem is not really with the ODBC driver, but with the Office update and how it 'cooperates' with the ODBC driver. He has therefore deactivated the Office C2R updates via the registry, so that the latest version is not immediately applied. Anyone else with such experiences?
Addendum: There are others who observed this, see the comments to my German blog post.
Cookies helps to fund this blog: Cookie settings