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

    We stopped rolling out new compiled version.

    Customers running Access Runtime 2016 Version 16.0.15330.0.20246 can't run the accde which is compiled in Microsoft 365 Apps for Enterprise Access Version 16.0.15330.0.20246.

    It is dramatical now!

    Wolfram

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-07-18T09:45:53+00:00

    Hi scottgem,

    We stopped rolling out new compiled version.

    Customers running Access Runtime 2016 Version 16.0.15330.0.20246 can't run the accde which is compiled in Microsoft 365 Apps for Enterprise Access Version 16.0.15330.0.20246.

    It is dramatical now!

    Does MS stop installing this Updates / Patches??

    Wolfram

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-07-18T15:04:54+00:00

    Hi Wolfram, could you try it and see if it's working? For some reason my ability do output to html or anything else quit working and I was curious if this is something also affected by this recent update. It generates a error 2587 and will not ouput. Thanks

    The visual basic code you entered contains a syntax error or the output procedures are not available

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-07-18T15:30:39+00:00

    Hello,

    well as we know, MS is aware and working on a fix. We're also aware and working on going to Mars one day.

    Thanks to everyone that has suggested workarounds but unfortunately none worked for us. The one that seemed most promising was to recompile the ACCDE file with the updated Access. However, we were not able to do that as our Access project relies on references to another ACCDE (third party solution) and Access was not able to read the reference to the ACCDE reference so compile would fail.

    The only thing that worked (very well actually) was to roll back office to the version prior to the update. Unfortunately we have Office 365 Click-to-run (CTR) so there is no easy was to uninstall an update (via Windows uninstall for example).

    I just wanted to share how we did this in case it can help others get up and running. It literally takes less than 5 minutes.

    1. download and run the Office Deployment tool here : https://www.microsoft.com/download/details.aspx?id=49117
    2. Install in an easy access directory like C:/Temp

    3 ) Open Notepad and paste the following:

    <Configuration>

    <Updates Enabled="TRUE" TargetVersion="16.0.15330.20230" />
    </Configuration>

    1. Save the file as config.xml in the same directory as were you installed the Office Deployment tool in step 2
    2. Open an elevated command prompt (Start, cmd, run as administrator)
    3. Using the DOS prompts, navigate to your directory from step 2 and run the following command:

    setup.exe /configure config.xml

    1. Once the update is downloaded and finished, open Word or Excel and go into File > Account
    2. In the product information section, Update options > Update now (this will do the revert)
    3. Although MS has probably stopped rolling out the problematic update, you should turn off automatic updates for a while to prevent an auto-update back tot he problematic version.
    4. To do this, File > Account > Product Information > Update options > Disable updates

    That's it, you're back to before the nightmare.

    In step 3, we revert back to version 20230. Depending on your type of Office, it might be something else. You can find the version history here : https://docs.microsoft.com/officeupdates/update-history-office365-proplus-by-date?redirectSourcePath=%252fen-us%252farticle%252fae942449-1fca-4484-898b-a933ea23def7

    All the info above is taken directly from MS Support here : https://support.microsoft.com/en-us/topic/how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841

    In the end, it is still a pain to do this on numerous machines but it is a fix that does 100% work. It might be easier in the end to do this without having to change any coding in your Access project and will insure that everything will work once the fixed patched is released.

    Finally, please note that once we reverted, our Access project would still not compile because the update had broken our references to the ACCDE our project depends on. Once we fixed the references, everything was working.

    Good luck.

    Mike

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-07-18T15:55:27+00:00

    Dear Kevin62,

    sorry, I think you wrote to wrong person. I didn't provide any VBA.

    As answered before, we don't do HTML export.

    regards Wolfram

    Was this answer helpful?

    0 comments