Problem with the MsJet40.dll released with the Windows 10 KB4566782 Update

Problem Solved

Thanks to Microsoft Teams

Tomy41 

YEP,

It seems my replicated MS Access 2003 .mdb work as used.
Thx to Microsoft for the solution and staying on the path to support older products.

btw. - I made a copy of that 'good working' msnet40.dll version 27 and added it to my collection 20, 24.

@alle

Gute Nachrichten 🙂 

Mit dem aktuellen Update (KB4571756) wird die msjet40.dll auf Version 4.0.9801.27 aktualisiert.

Diese scheint nun wieder korrekt zu funktionieren, auf unseren Testsystemen können replizierte Datenbanken geöffnet werden. 

Hi,

Sorry, but I'm not aware of any public announcement in this matter so far.

You can have a look at the reply a poster gave in this thread on Sep 2 and hope he's right.

Karl
*********
http://AccessDevCon.com
Access FAQ (German/Italian): http://donkarl.com

Karl_Donaubauer 

Due to the MSJET40.dll 4.0.9801.25 still is fixing, I would like to suggest that Access Dev Team takes out MSJET40.dll 4.0.9801.25 and puts back  MSJET40.dll 4.0.9801.24 in both KB4566782 Update and 
KB4565351 update (may be more KBxxxxxxx) until the issue has been fixed.

Hi,

Another attempt to make my point clear which is not about the known fact that you can't open the replicated MDB files:

Did you do the replication by code from outside of Access (by programming it from wherever) or did you always and only work with the MDBs from within Access?

If we get several reports about this aspect, it would make the difference between an Access application problem in very old and unsupported versions but at least Access or a Windows problem that by accident affects MDB files. This distinction may not be easy to understand but it makes a difference in some respect (and I've tried my best until exhaustion ;-).

Karl_Donaubauer 

As I wrote, I just double clic on the file, and msaccess.exe can't open the mdb entire file anymore, since it contains replicated tabes on it

Accessing data from outside does not work too

Is there anyone working with msaccess team here, so I can send him a mdb file to open ?

Hi,

It's not that simple that just someone "has to correct his bug". We are talking about versions and features of (maybe) Access that are many years out of any support and the JET dll is part of Windows not of Access in the first place. So I would like to ask about your use case again:

Point 3 is clear as you mentioned Access 2000. But how about 1+2? Mind, there is a difference between opening up an MDB one time with Access to control it or really working with fully fledged Access applications and experiencing the problem.

1) Is it that you or your users open Access to manage replicated data in an Access frontend with forms, queries etc. and it is there where they experience the replication related problem, i.e. they cant't open their Access application with Access any more?

Or

2) Is it that you just use MDB files to hold data and pilote the MDB files and replication (i.e. msjt40.dll and msjro.dll) from outside of Access like with a VB or .NET etc. application? So there is no real Access application involved, just MDB files.

Microsoft told me to write here , and here they are telling me to write to microsoft !

This is very simple. The developper who changed the msjet40.dll code from version .24 to .25 need to correct his bug

This dll is the msjet database engine used by msaccess mdb and is automatically updated by Windows update 

The bug is very simple to reproduce, when you double clik on a MDB database file that is replicated, then msaccess can't open it anymore

I personnaly still open mdb database with msaccess 2000 exe, but I think it is the same with all msaccess versions, or openning the database by code