This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
A family of Microsoft relational database management systems designed for ease of use.
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.
Hi Shane
just tested on one computer here. Can confirm error is solved, old compiled version starts as usual.
Thank you, helps a lot. Do you have a hint, how customers should act to make sure update to latest version can be forced?
regards Wolfram
Hi Shane
Confirming that the fix worked for Access in Office 365. Eagerly waiting for solutions in other versions (and for Mars trip too).
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.
I promise we'll get a fix out before someone gets to Mars.
If you are on Current Channel use File/Account/Update Options/Update Now, that should move you to build 15330.20264, which has a fix for this issue.
Other channels will be updated soon.
Shane Groff
Access Engineering
If you are using Office 365 Current Channel, which is Version 2206, there is an update available, which you can get by choosing File/Account/Office Updates/Update Now. This should take you to Build 15330.20264.
Shane Groff
Access Engineering
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 51%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Anyway.. shame on you, Microsoft!!
Very little of what you ranted about is true. Yes you pay a good deal of money for licenses. But no, they are NOT "pushing updates, without any info". They are not deliberately shutting production applications. They are not forcing you to pay anything more. The update that caused this was a security update that there is no charge for. That it did cause an issue is unfortunate, but its a reflection on the complexity and interoperable of Office and Windows. A complexity and interoperability that is part of the reason for the populatiy of both software products.
There is no hidden marketing tricks here. Software gets improved, file types get improved. Microsoft tries to maintain a long term backward compatability, but can't do it forever. Other software developers don't do that.