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. ScottGem 68,840 Reputation points Volunteer Moderator
    2022-07-19T17:49:53+00:00

    That Microsoft should have tested more, I won't dispute. But the rest of what I said holds a lot of water.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-07-19T15:23:02+00:00

    Hey All,

    Having the same issue and all users are using Office 365 apps. We have now narrowed down the issue to be with any user using Microsoft 365 Apps for Business as the Enterprise version is working. I have tested this on a spare laptop to confirm our findings. I'm not sure what the difference is between the two but MS Access is working for the user using Microsoft 365 Apps for Enterprise.

    Now we just need a fix for the Microsoft 365 Apps for Business users as upgrading for us is not the greatest solution.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-07-19T15:22:38+00:00

    We had one client experiencing the problem who was signed up as part of the Office Insider program. Yet he was updated with the faulty software AFTER others who were not part of Office Insider. It doesn't take a cynic to suggest that it should be the other way round.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-07-19T11:55:23+00:00

    That fixed the Output from Reports issue for me, now on 15330.20264. (error 2587)

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-07-19T10:36:08+00:00

    This is amazing, with all the talk that Ms Access is dead as a software application. This issue has shown me how useful and popular this software is and that MS Access is not going away any time soon.

    Was this answer helpful?

    0 comments No comments