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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-07-14T13:53:17+00:00

    If anyone is looking for a solution for the time being, I found something that works for me.

    If I create a blank form with no codebehind, and add an extra step at the beginning of the AutoExec macro to open that form first, and then open the real form afterward, it does not throw any errors. I can then add another step in the macro to close that blank form and continue on my way.

    (last time microsoft broke access with a security update like this it took them over a month to fix it, so I started looking for ways to deal with it)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-07-14T12:27:22+00:00

    With regards to the July Microsoft patch Tuesday updates rolled out yesterday it's not just update KB5002121 (Security Update to Microsoft Office 2013), it is also caused by KB5002112 (Security Update to Microsoft Office 2016).

    The issue applies to compiled databases (e.g. MDEs etc.), not uncompiled (MDBs) that I have seen, and is not limited to the runtime versions of Access as I first thought unfortunately.

    You do not need to uninstall Access (unless one of the many other updates not mentioned here break your databases as well), just uninstall the relevant VBE7.dll file update, as above.

    FYI there were other updates that updated some of our other dependencies such as MSO.dll, ieframe.dll etc, so it depends what other references you are using but it was only the VBE7,dll update that fixed our database issues.
    https://www.reddit.com/r/MSAccess/comments/vy5wtr/issues_with_kb5002112kb5002121_vbe7dll/(this was my original post on this)

    Was this answer helpful?

    0 comments
  3. Günter Born 49,461 Reputation points
    2022-07-14T09:01:56+00:00

    Just as an addendum - not sure, whether the team is aware (hadn't reported yet, but several of my blog reader). A summary may be found at.

    Office updates destroys Access run time and apps

    There are also a couple of comments from affected users within the cross linked German blog post. It affects Office 2013, 2016 (MSI) and also Office 65 (C2R).

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-07-14T05:51:12+00:00

    Please withdraw the faulty KB5002121 update NOW!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-07-14T05:19:37+00:00

    Thank you Giorgio, it helped.

    Was this answer helpful?

    0 comments