I can't take them offline because they sell goods over the Internet to a large customer base. They have been using this ADP application for 21 years, and they will retire in a few years.
I don't want to discuss the details here. I just want to say that it's not as easy to adapt for some of us.
It's clearly a software regression type of bug.
And it's not an ancient file.
The newest Windows 11 update KB5064081 has replaced the DLL file C:\Windows\SysWOW64\msjtes40.dll with a new version.
The old version was:
2024-04-01 09:22 290,816 msjtes40.dll Version 4.00.9801.0
The new...
Thanks, but it's not only ADOX but also simple ADO (see #21).
And the bug also occurs with the newest Access 365 (32-bit) under Windows 11 (with the newest update) and probably with other VBA code (Excel, Word) or other programming environments using ADO and Jet (i.e. provider...
My conclusion is:
The error is in version 10.0.26100.5074 of C:\Windows\SysWOW64\msjtes40.dll (32-bit).
This version of the DLL is installed by the August 29 Windows 11 update KB5064081.
The DLL is used when Access is 32-.bit and the ADO provider is "Microsoft.Jet.OLEDB.4.0".
It's a low level...
Sorry, I made a mistake with the 32/64 bit Access versions. I only tested with 32-bit versions of Access.
I tested with:
Access 365 v2507 19029.20208 32-bit.
Access Runtime 365 16.0.19127.20154, 32-bit.
Access Runtime 2010 32.bit. (Still in use for a very large old Access Project application...
I have the same problem on several computers with Win11 and KB5064081. Different Access versions, but only 32-bit Access/Office.
My workarounds found until now (while still using ADO):
Use ACE provider "Microsoft.ACE.OLEDB.12.0" instead of "Microsoft.Jet.OLEDB.4.0"
Uninstall KB5064081
My test...