I can confirm it for the following Monthly Rollup:
- KB4480970 (Monthly Rollup) january 8, 2019, Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1
- KB4480963 (Monthly Rollup) january 8, 2019, Windows 8.1, Windows Server 2012 R2
- KB4480966 (Monthly Rollup) january 8, 2019, (OS Build 17134.523) Windows 10, version 1803
- KB4480116 (Monthly Rollup) january 8, 2019, (OS Build 17763.253) Windows 10, version 1809, Windows Server 2019, all versions
And after some trail and error we found out the problem, occurs with using JetEngine 3.6 (or higher?) to open an Acces97 database and the table contains a fieldname which has more than 32 characters. Tables which don't contain fieldnames with long names
are still able to open.
Maybe there are some more situations, but this is what we found.
Using JetEngine 3.51 (the 'native' Access 97 driver) there doesn't seem to be any problems.
So if you're using a connectionstring like:
"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=<MyAccessDatabase>.mdb"
It might be solved using the following:
"Provider=Microsoft.Jet.OLEDB.3.51;Data Source=<MyAccessDatabase>.mdb"
Haven't tested it, but we tested the problem with DAO 3.51 and DAO 3.6 in ou software, and DAO 3.51 works, DAO 3.6 doesn't.
**Edit: I can confirm that OLEDB.3.51 resolves the problem of reading (but I don't if it might have problems generating a database, the code I have does have problems on adding an Index, but at other points it did have special 4.0 additions, so I need to
check it further if I need to change stuff).
**Edit: mind you, for provider Microsoft.Jet.OLEDB.3.51 to work you'll need to have it installed, where 4.0 comes pre-installed with windows, 3.51 doesn't.
**Edit: Just tested the following provider and it seems to work like the Microsoft.Jet.OLEDB.4.0 provider (with the ACE version could create an Acces97 mdb without any errors), :
"Provider=Microsoft.ACE.OLEDB.12.0;Data Source=.\<MyAccessDatabase>.mdb;User Id=admin;Jet OLEDB:Database Password=<MyPassword>;Jet OLEDB:Engine Type=4"
....Sigh... OLDEDB.12 doesn't work anymore after AccessDatabaseEngine 2016 is installed, due to the provider being pointed to the DLL of Office 2016 which doesn't support Access97 anymore (thanx Microsoft for doing something stupid like that), only way to
fix that, is manually change the link back to the original DLL.