Yes, once again (I know I’m sounding like a broken record – not my fault, speak to Microsoft!), Patch Tuesday has gone and messed up the jet dll (msjet40.dll).
Symptoms
Some of the symptoms include:
- uncontrollable database bloating
- errors relating to ‘MSysAccessObjects’
- breaks replication
- …
Who’s Impacted by This Bug
Impacted system are those still using Jet, so any of the older mdb, mde style database.
Source of the Problem
Windows 10 KB4566782 Update appears to be the root cause of this latest headache. KB4566782 updates MsJet40.dll to version 4.0.9801.25 which obviously is the culprit here.
Someone else has stated that the issue comes from Office Update KB4565351.
Not that it make any real difference to you at the end of the day, but as this is a Windows 10 update that caused this latest issue (same thing for the ‘Unrecognized Database‘ error that has been plaguing us for over 2 years now with still no fix! Someone needs to desperately speak to the Windows 10 Team and introduce them to QA/Testing!), indicates that this update did NOT originate from the Access Dev Team, but it definitely directly impacts them. Probably a case of the right-hand not talking to the left-hand. One thing is for certain, the update was definitely not tested!!
Solution
The solution is to revert the MsJet40.dll to a prior version. Some people are copying an older copy of the MsJet40.dll file from other machine that haven’t been updated yet.
Personally, I would rollback KB4566782 and/or KB4565351 completely at this point in time.
What I can say is this affects Jet which appears to impact certain mdb databases, thus we are talking about Access 2003 or prior. These versions are all out of support and thus Microsoft can simply state that they no longer need to worry about them. So it will be interesting to see the actual outcome of this particular issue.
What Can You Do
As always, get yourself heard is about the only thing you can do! So
- Post on forums
- Use the Feedback command from within Access to express yourself
- Post suggestions within access.uservoice.com
So express yourselves, tell Microsoft how much this has impacted you. If you don’t they will just continue business as usual. If you want things to change, speak up now or forever hold your peace. Remember, the squeaky wheel gets the grease.
A Few Threads on This Issue
Here are a few recent posts about this issue: