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-14T18:55:12+00:00

    Hi RolandTMS,

    this was our first try. But in our situation didn't solve the problem.

    But from "A Real Human"s answer
    "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."
    Comibined with our test and watching not too early to start the code

    • My first try tomorrow will be his solution, may be with an extra 2 seconds delay inbetween.

    kind regards

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-07-14T18:53:16+00:00

    This has happened to me also for an important directory database I use constantly. After latest Microsoft 365 update, I get the "Requested type library or wizard is not a VBA project." I did not compile the database structure, so dont know how to correct my current lack of access to my data.

    Was this answer helpful?

    0 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
  4. Anonymous
    2022-07-14T16:37:43+00:00

    We could see this on customers running our app with Access 2016, 2013 and also those using Access out of Microsoft 365 (here Version 2206 brings in this behaviour).
    Dramatically as we talk about more than 1000 computers in Europe and Asia!

    If you set Options , aktive database, open form on startup to "no form" (all translated, english might be different in Office) It works.
    However in most cases the startform will call procedures for connection, login... so not posisble to do.

    We found a dependency to form complexity. A simple form in open event only a message box works. But if in open a call for functions in modules exists, the error comes up.
    Latest workarround: simple form in options, on simple form a button to call the original start form. Test in the smaller app with Microsoft 365 Access was acceptable. simple form opend and on click opened the real form. However we noticed if you click immediately after form is visible you get the error and have to click twice.

    Was this answer helpful?

    0 comments
  5. ScottGem 68,840 Reputation points Volunteer Moderator
    2022-07-14T14:01:26+00:00

    Thanks for posting that solution. However, as I recall the last time there was a major bug was a few months ago and it was fixed within a couple of days transparently to the users. There was an issue last year, that did take several weeks to produce a fix.

    Was this answer helpful?

    0 comments