Forum Discussion
Problem with the MsJet40.dll released with the Windows 10 KB4566782 Update
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.
I pretty sure and definitely that the problem is related Windows 10 because the problem occurred since Windows automatic updated by KB4565351, At the same time the MSJET40.dll is updated to version 4.0.9801.25, afterward we could not open my Accesss program, we needed to rollback to MSJET40.dll 4.0.9801.24 then to be back to normal working.
For My Case:
I am using Access 2000. One frontend MDB including many forms, report and queries to connect a backend MDB which is as database including all db tables. No others and it is so simple.
Problem with MSJET40.dll 4.0.9801.25 :
I just clicked the frontend MDB, it will show below error message:
"Unable to open database 'MSysAccessObjects'. It may not be a database that your application recognizes, or the file may be damaged "
I know i am using a old Access 2000, but the problem absolutely is related to Windows updated then cause this bug and issue.
I am grateful for Access Dev. Team helping to fix the bug.