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.
Newest problem:
Just some minutes ago customer running app with old 2010 reported next problem: 2010 is not able to read that accde. And reprts unknown database format (we use 2007 - 2016).
I tested this here and can confirm the problem.
Hi Massimiliano Zuffi,
we allready started (with biggest customer > 100 Computer) to sent out Updates compiled in version with kb5002112. Our automatic update at customer is driven from the app itself. So we nned to run update BEFORE kb5002112. Otherwise customer needs manually to update each computer.
Just some minutes ago customer running app with old 2010 reported next problem: 2010 is not able to read that accde. And reprts unknown database format (we use 2007 - 2016).
Wolfram
I've about one hundred customers with almost 5 pc each one, with different version of Access, with a big Microsoft Access application. So, I've about 500 pc with various version of Access. This application is constantly upgraded so, with an automatic system, I send every 2 weeks an upgrade to my customers. The upgrade overwrites the previous version of the accde. For someone I've recompilated the program with the right version of Access, but I can not think that I've to do that every 2 weeks for all my clients (every client has a customized version of the program, so I can not compile one version for all). Could I have a rapid solution for this problem?
Sorry to hear about the work load this creates in the interim. I am also waiting on Microsoft Office to fix the issue as it is not practical to recompile all the databases that have been deployed. I wish more testing is done before these updates are released given that this is not the first time these updates have caused issues to MS Access.
Hi Scottgem,
we are doing soltution "recompile" as also Microsoft lists this as solution.
However our app has customer specific module, whh is different for every customer. So we need to do this for more than 120 active customers many need both 32bit and 64bit.
A very big workload for us and the customers for rolling out.
And danger for customer if Patch (or 365 Update) happens before they have our update, they need to update each client manually. Big customer up to 100 computers! (normally we have an automatic update).
Any information, if Microsoft will stop Patch for some days, to give users a chance to update before it rolls out?
Wolfram