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.
This is amazing, with all the talk that Ms Access is dead as a software application. This issue has shown me how useful and popular this software is and that MS Access is not going away any time soon.
That fixed the Output from Reports issue for me, now on 15330.20264. (error 2587)
Sorry Scottgem, doesn't hold water. For something as fundamental as that error (mde/accde not being able to run) Microsoft should be putting in more testing. The cost to us, in terms of assisting clients, and the cost to our clients in terms of down-time is way beyond any benefit that the update would have given us. Please don't release software that doesn't work!
A cynic might suggest that the testing is still being done. It's now "post-release testing" by customers as opposed to "pre-release testing" by MS, but it's still happening.
We had one client experiencing the problem who was signed up as part of the Office Insider program. Yet he was updated with the faulty software AFTER others who were not part of Office Insider. It doesn't take a cynic to suggest that it should be the other way round.