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-15T19:18:17+00:00

    Here is the link to the page that has the affected versions/builds, and that will be updated with fixed build/version numbers when they are available:

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

    The only workaround it mentions is that you can recompile the ACCDE with the target version of Office. Some users have reported that they have been able to modify applicaitons (e.g. by using an Autoexec macro, rather than a Display Form to open an initial form), but these workarounds don't work in all cases, so we haven't included them in this page.

    Shane Groff

    Access Engineering

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-07-15T16:47:51+00:00

    There will be a page posted here: Fixes or workarounds for recent issues in Access (microsoft.com)

    Shortly that lists all the affected builds. That page will be updated with information about the fix when it is available.

    I'll post the direct link to the page once it is published.

    Shane Groff

    Access Engineering

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. ScottGem 68,840 Reputation points Volunteer Moderator
    2022-07-15T16:00:09+00:00

    A fix like this is rolled out automatically. Most likely the Access team will post it here.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-07-15T15:49:04+00:00

    How will Microsoft notify the community that this CRITICAL BUG is fixed?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-07-15T11:49:35+00:00

    Latest research:
    Office 2016 MSI with latetst Update shows Version 2206 16.0.15330.20246 for 32 bit
    same version is shown on Microsoft 365 Apps.

    Theese don't get Patch kb5002012 as extra entry in recent updates

    Runtime is handeled different. Cusstomers with Runtime see Patch kb5002112

    Patch removal solves the problem immediately for now.

    Error only comes with accde, not with accdB.

    If we compile unchanged accdb in updated office version (with the error) I can confirm what someone posted: this new compiled accde works without error.

    I expect this options:

    • MS stops install of 2206 (don' t belive)
    • MS provides a fixed version to update 2206 (may take time)
    • We app vendors need to send updates to all customers kompiled with new version
      (we will do for big customers)

    regards

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments