KB5002121 breaks MS Access runtime applications

Anonymous
2022-07-13T19:05:58+00:00

I just had a lengthy support call with a client. My MS Access (mde) file would not open. Received the message: "The expression on open you entered as the event property setting produced the following error. Requested type library or wizard is not a VBA project." I uploaded the uncompiled (mdb) file and that one ran fine. I tried creating a new mde file but it too would not run. After much head scratching, I check the latest updates and saw the following update installed today: Security Update to Microsoft Office 2013 (KB5002121) 32-bit Edition

After uninstalling the update the application ran perfectly fine. I have no other conclusion than this update caused it not to run. My client has temporarily turned off the automatic updates. Can anyone else confirm this issue?

Microsoft 365 and Office | Access | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

95 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-08-12T19:06:00+00:00

    For what it's worth, I have tracked the issue to VBE7.dll in C:\Program Files (x86)\Common Files\Microsoft Shared\VBA\VBA7.1.

    Some PCs will not open a Access RT application after the update in question .However, replacing this DLL with an older one from Last November seems to fix the issue. I have applied this fix multiple times now with good results.

    I am not sure why some PCs experience this issue but when it occurs, replacing the dll has worked every time so far.

    Please don't do that, it is not always safe to mix and match dlls.

    See: Error when trying to open an ACCDE/MDE file created in a different version of Access (microsoft.com)

    And get the update that fixes the issue for you depending on what version/channel of Office you are using.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-08-12T19:28:19+00:00

    Ran the update and I see that VBE7.dll was replaced. So the hack/fix is no longer needed.

    Thanks

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-08-17T17:44:56+00:00

    Yes, I can confirm that one of my Access database (running with ACCDE) has also experienced failures (database corruptions) after the patch was installed this week. Initially, a customer reached out about the error which I could not duplicate. I installed the patch yesterday morning and abra-cadabra, I could corrupt the database, too. Reaching out to my I.T. department for help with a rollback now. Thank you for identifying the issue!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-08-17T18:04:19+00:00

    I am glad you found it helpful. I have created a very simple, stripped down new Display Form that pops up when the app is opened. It informs the user to wait ~5 seconds before clicking on the button to go to the Login screen. This is my work around until our very large IT group gets around to installing the patch from Microsoft to correct the issue.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-08-18T12:42:22+00:00

    I had / have the same issue with Access 2013/

    • uninstalled Kb5002121 + reboot -> Didn't help
    • installed fix KB5002250 + reboot -> didn't help

    i got it "solved" by copying 2 old DLL's from a computer that hadn't received those patches.

    (DLL's are noted in the eventvwr error)

    C:\Program Files (x86)\Common Files\Microsoft Shared\VBA\VBA7.1

    files: VBE7.DLL + VBEUI.DLL.

    -> Bad version date: july 2022

    -> Working (older) version date: nov 2021.

    Curious how long it will work, and if a new patch will keep it working.

    Was this answer helpful?

    0 comments