KB5002121 breaks MS Access runtime applications

Anonymous

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?

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

Anonymous

2022-07-18T21:05:21+00:00

Hi Shane

We have a system that is used by almost 500 different companies. They have different versions of Access and it has been a nightmare over the last week dealing with support calls to fix the issue. We were unable to tell customers to wait for a fix as the database is payroll related. We have had to rebuild the MDEs on the client computers.

For now the problem is managed, but please give us a solution so we don't have to do this every time we update our application.

Sorry to add this here... but could you also please comment on the Excel report problem that also appeared after the latest update.

Since latest Microsoft Update: Access (Office 365) unable - Microsoft Community

The Excel report is a critical component of our application for many users.

Thanks

Sanjay
Was this answer helpful?

0 comments No comments
Anonymous

2022-07-18T20:49:12+00:00

Hi Shane,

i am again. We have to recompile and sent out over 100 customer versions. This needs time.

Can you organize pause for installing the critical updates?

Just for this week ?

regards

Wolfram
Was this answer helpful?

0 comments No comments
Anonymous

2022-07-18T20:44:50+00:00
Dear Shane,

my post had two directions:
1. information to others having customers with old version
2. Access time should rename the format from "2007 to 2016" to "2016 to 365"
to make clear 2007, 2010 are out of scope.

I clearly can understand support end, we do so also. SQ -Sever and Access, but as you know in real world...

Wolfram
Was this answer helpful?

0 comments No comments
Anonymous

2022-07-18T18:18:57+00:00

Anyway.. shame on you, Microsoft!! We pay a lot of money for licenses, Office and Windows, and what you are doing? You are pushing updates, without any info, that could shut down production applications in some process computers, only to force us to update and pay more for the same type of applications, like Access, but just with other extension, for marketing reason!

Shame on you!!
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2022-07-18T17:58:29+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.

A fix will be released. The timing will depend on what version and channel you are using. As I posted on this thread previously, this page https://support.microsoft.com/en-us/topic/error-when-trying-to-open-an-accde-mde-file-created-in-a-different-version-of-access-f4cd36cd-549e-42ba-b75a-dfe964294a81 will have the information about how to get a fix when it is available.

Shane Groff

Access Engineering
Was this answer helpful?

0 comments No comments