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-18T16:05:49+00:00

    Dear M Allan,

    we also don't follow the recompile way any longer. It does not work for installed Access Runtime and on customers still running 2010 it is seen as "unexpected database format" (though Format 2007 to 2016 was selected).

    What we found as working is this approach:

    1. remove original start form
    2. insert a siple new form with one button 2a. button on_click event has only this (betwwen error handler): 
      DoCmd.Close acForm, Me.NAME 

DoCmd.OpenForm "your\_standard\_start\_from"

    no other code!

    1. select this simple form as start form
    2. compile and test

    We found only two small issues:

    a) if clicking before acces really open the Patch error comes up, but works on second click

    b) it is one additional click for users on starting the app

    Hth Wolfram

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-07-18T16:20:14+00:00

    Hello Wolfram,

    unfortunately that type of solution did not work for us as we were unable to compile our project so we were not able to create a new form (or anything else). Our project has references to another .accde file and because of this any compile would fail.

    Also, in our case we prefer not creating temporary forms like this as eventually when this problem is fixed we would need to delete this workaround dummy form and then recompile and redistribute. A lot of work versus simply re-allowing automatic updates on Office.

    Thank you for your feedback.

    Mike

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-07-18T16:33:51+00:00

    Hi Allan,

    I dislike the additional form also, but actually the only solution to give something to more than 100 customers (before patch is installed or office update running).

    Patch removal and office rollback will not be accepted by some customers (big automotive companies).

    Form is only inserted in each customers last version, on next update from source control it will not be present.

    I expect we will need until end of week, from big to small with in between of small reporting the problem.

    Wolfram

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-07-18T17:03:03+00:00

    Note that Access 2010 is no longer in support, which means

    1. It was not impacted by the change that is causing a problem for supported versions (2013 or later), since we aren't making any changes to Office 2010, including the one that introduced a problem.
    2. It may break at any time, and it won't be fixed because it is no longer supported.

    If people are using Office 2010 (including the 2010 Access Runtime), they need to be aware that it is not supported, and any issues that occur will not be addressed by Microsoft.

    Shane Groff

    Access Engineering

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-07-18T17:44:06+00:00

    Shane - The Workaround is not feasible. Can MS not provide a decent fix? If an update to our clients' machines, whether that be an update to their runtime or installation of a new KB would correct this, then please, set up a web page that we can direct them to.

    Was this answer helpful?

    0 comments