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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-07-15T06:05:15+00:00

    Hope you find a solution. Some customers have the app on 100 computers.

    What our experiment shows:

    It depends somehow on code in start form

    • only msgbox in Open event works
    • only a Button with on click openening real form works

    Hth

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-07-15T06:02:17+00:00

    Hi,

    I tried this approach as variant of workarround. Customer with 2016.
    It fails for our application.
    Emty form is opened by autoexec, but the same error comes up.
    Actually seems to work is this: extra startform with Button entered in Options as start form.
    When user clicks button, original start form is opened. Worked in 365 and 2016 with the smaller application. However if user clicks very fast after seeing extra start form, it also throws the error.

    Regards

    Was this answer helpful?

    0 comments
  3. ScottGem 68,840 Reputation points Volunteer Moderator
    2022-07-14T19:03:48+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.

    There have been several workarounds offered by users here. I would suggest making a copy of your application and testing those workarounds to see if any work for.

    Was this answer helpful?

    0 comments
  4. 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
  5. 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