Forum Discussion
Problem with the MsJet40.dll released with the Windows 10 KB4566782 Update
Daniel_Pineault No, this is a very new problem with the new August 2020 Windows 10 update. The database are not corrupted, but can't be openned with the new msjet40.dll.
Reverting to the previous version of the dll, and the database can be openned
Daniel_Pineault Thank you ! let me know when you get an answer from the great Access Dev Team
For now, we need to replace the new msjet40.dll by the old one to 3000 users... As they all call us because our program does not work anymore
For this, we need to change the owner of the file from TrustedInstaller... and paste the old version of the file
Not very clean...
Danke für deinen Hinweis auf die MSJet40.dll, hat mich auf den richtigen Weg gebracht 🙂
Auch wir verschwenden nun unsere Zeit damit, an Hunderten Arbeitsplätzen unserer Anwender diese dll zurückzusetzen.
Hoffentlich wird hier bald eine Korrektur erfolgen oder ein eleganterer Lösungsweg aufgezeigt.
The issue must be fixed asap by Access Team. I am afraid my Access Program getting same problem again later, because Microsoft will be automatic updated suddenly, thus, I need to repeat the MSjet40.dll restoration.
Please Access Team!
PatrickLee2195 OChristiaanse Dan2000 and all other affected people:
For the discussions with Microsoft it would be helpful to know to what extent you are talking about real Access applications. Therefore a few questions:
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.
3) If Access is really involved, which version(s) of Access do you use?
Hallo,
ich glaube, das Problem sollte im Windows-Bereich bleiben oder zumindest dorthin verlinkt werden.
Es handelt sich ja hier offensichtlich um eine Fehlfunktion der msjet40.dll, die Bestandteil von Windows ist.
Einige (so wie ich) verwenden ja gar keine Access-Anwendung sondern benutzen nur mdb-Datenbanken für die Datenspeicherung.
