Access – MDEs & ACCDEs Breaking

Software Bug

As reported to me earlier in the day (by Mark D) and now confirmed by multiple sources, it would seem we have another bug to add to our long list impacting MDEs & ACCDEs .

You know you’ve been impacted by this issue if you receive the following error 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.

another report presented the error as being:

The expression you entered as the event property setting produced the following error:

The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure]. There may have been an error evaluating the function, event, or macro.

This appears to impact:

  • MS365 all versions (July 12, 2022 update) – It is widespread and the build varies depending on the Update Channel you are using
  • KB5002121 for Office 2013
  • KB5002112 for Office 2016

Workaround

The only known workaround at this point in time is to uninstall the faulty KBs or revert your build to a prior ‘stable’ build.

Where’s Microsoft in all of This?

I notified them earlier this morning of the issue, when I first got wind of it.

2022-07-15 – We now actually have a Fixes and Workaround page on the subject!  You can find all the impacted MS365 build numbers.

Error when trying to open an ACCDE/MDE file created in a different version of Access
When opening an ACCDE/MDE file, users may receive an error message with the text “Requested type library or wizard is not a VBA project.”

 

Forum Discussions on the Subject

If you’re a sucker for punishment and want to see what others are saying on the subject feel free to look over:

KB5002121 breaks MS Access runtime applications
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."
Msaccess - Office Update - Version 2206 Build 15330.20246
Access365 / 2019 received the latest office update, current channel, Version 2206 Build 15330.20246.

This issue has also been reported to us on monthly channel (Version 2205 Build 15225.20356) and semi-annual (Version 2202 Build 14931.20604).

Since the update we get the following error in our application at startup.
Update KB5002121 causing problems with A13 Runtime?
Today I had 2 clients who had problems using my application that runs with A13 Runtime. They could not enter the application. The problem was solved when I removed KB5002121. Do we have any news about this update?
Update KB5002121 causing problems with A13 Runtime?
I have had one client contact me with an error message when trying to open A2013RT.
Jul 12, 2022 Microsoft update has broken my Access app
I have an Access app that has been around for almost 20 years which I continuously update and support and is used as a POS in about 35 stores. This Tuesday I received calls from several stores that the app no longer starts up. Since then I have been busy dealing with these issues and trying to get my customers' POS running again.

7 responses on “Access – MDEs & ACCDEs Breaking”

  1. Leslie Desser

    These three lines in a batch file will re-install 2205. It MUST be run as Admin.
    The 2nd line turns off future update to Office
    The 3rd install 2205

    cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun
    OfficeC2RClient.exe /ChangeSetting updatesEnabled=False 16
    officec2rclient.exe /update user updatetoversion=16.0.15225.20288

    1. Dennis

      Hi, I ran that on one of my client’s PCs and it fixed the issue.

      I tried to run it on another client’s PC, it appeared to run the batch file but it did not initiate the rollback.

      Do you have any idea why that may be (I am wondering if it’s a policy thing that their IT company have imposed to stop people running code in specific folders?)

      1. Daniel Pineault Post author

        Yes, IT policies can’t stop you from being able to make such changes.

        Also, the recent bug has different builds depending on the Update Channel, so you can’t revert to the same build for all. You need to lookup your Update Channel’s updates, and revert appropriately.

  3. Demi V

    The same code for Office 2019 (broken version is 16.0.10388.20027)

    cd ‘C:\Program Files\Common Files\Microsoft Shared\ClickToRun\’
    .\OfficeC2RClient.exe /ChangeSetting updatesEnabled=False 16
    .\officec2rclient.exe /update user updatetoversion=16.0.10386.20017

  4. Leslie Desser

    We now have a client with a server with o365 on Semi-annual enterprise channel who restarted their server and can no longer open Access.
    They are on 2202 14931.20604 Click-to-run which the MS site shows as last updated 12 July. The restart must have installed it.
    Does anyone know how to revert back to 2201?