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 No comments

95 answers

Sort by: Most helpful
  1. Anonymous
    2022-08-02T22:54:24+00:00

    The update that fixes this issue for Office 2013 and Office 2016 MSI is now available:

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

    Shane Groff

    Access Engineering

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No 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 No comments
  3. Anonymous
    2022-07-14T18:25:09+00:00

    Problem is solved by removing the default "Display form" completely at the "Current database" options and replacing it with OpenForm in the Autoexec macro (behind RunCode to load the ribbons).

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-07-13T19:55:23+00:00

    hi,

    I have several clients who use my access project, some with access runtime 2013 and others with access runtime 2016 but all with the same problem, my project is in accde format generated with access 2016

    bye

    Giorgio Rancati

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. ScottGem 68,840 Reputation points Volunteer Moderator
    2022-07-13T19:41:54+00:00

    I saw another poster report the same error.

    However, you don't say what Runtime version of Access is being used. If a Runtime is not being used (as the poster i referred to), what version of Access.

    And if they are using any version after 2010, why are you still using MDEs?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments