After i replaced \windows\syswow\msrd3x40.dll (08.01.2019)

by an older version, the problem vanished.

Hi karstenBock1,

many thanks for your suggestion.

We are doing so on both Win 10 and Win 7 successfully.

I hope that going back with Dll version, no other issues may appear elsewhere.

Thanks

Also working on Server 2016

Hello.

KB4480970 stopped a lot of our plant around the world, with production loss.

How Microsoft thinks to fix this issue?

Tks,

Davide Gardoni

Many thanks, it worked for me on W7 and W10

Folder: C:\Windows\SysWOW64 on 64 bit OS,    C:\Windows\System32 on 32 bit OS
Bad: version:4.0.9801.7 date:09/01/2019 09:35
OK : version:4.0.9801.5 date:25/09/2018 02:56

I had to change owner and permission to be able to replace the DLL.

I can confirm this issue also.  After installing KB4480116 I get "Runtime Error 3343 Unrecognized database Format" when trying to access a MDB that contains our HR data.  The program is no longer supported so I cannot convert the database to a newer version.  Uninstalling the update fixes the issue and I am able to access the MDB.

I am religious about keeping updates current on all of our machines but this one for now is declined for install in WSUS.  Hopefully the issue is resolved in a future update, and a future cumulative update does not break this again.

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.

Appears to be the same issue we are seeing in our software out in the field.  While we don't have individual column or table names with more than 32 characters, we have many queries that reference the column by tablename.columnname which results in more than 32 characters.  If we change the queries to reference the table name by a shorter alias the errors no longer occur.

Windows would not let me replace the file, said it had to be done by a trusted installer.

So it affects all supported Windows versions after the January 8, 2019 security updates has been installed, because the Jet Database Engine patch breaks access to MS Access 97 databases. I've summed up at: Windows January 2019 Updates breaks access to Access DBs.

I will escalate this thread to other moderators - hopefully someone of the MS forum moderators will forward it to Microsoft's developers.