[German]I got reports, that Microsoft Office 365 version 2206 (Build 15330.20246) is causing issues with VBA in Access applications. And I got reports, that KB5002121 for Office 2013 and KB5002112 for Office 2016 is causing the same issue.
1# Report on Office 365 issues
The first report I received via Twitter. The person in question thinks that Microsoft has once again ruined Access with an Office update and posted the following screenshot of the error message in a tweet – the German text means translated:
You have entered the expression On Load as the event property setting. This expression has caused an error: Requested class library or wizard is not a VBA project.
If you search for the bug, there are quite a few hits – and a support post from April 2022. From the post, I conclude that there was either a reference to a library disabled (you can find out in the VBA environment) or a reference broken by the update. Anyone else who happens to have this bug and can elaborate? The user replied on Twitter:
The error occurs with our customers who have installed update 15330.20246. It disappears when you revert to 15330.20230 OR create a new ACCDE with the newer Access version. This will then run on both builds, but not on older Office versions. By this I mean Access 2013 or 2010.
So it seems to be related to the latest update. However, the user also points out that build 15330.20246 is not yet listed in the Microsoft 365 update history. At this point, my thanks to the reader for the information.
#2 Report on Access Run Time issues
A short time later I received the notification within the following tweet, that an installed Access Run Time (RT) also seems to show these errors.
#3 Report Office 2013/2016 also affected
In another tweet, the first user reported, that the error occurs after installing Office 2013 update KB5002121 or Office 2016 update KB5002112. In all cases, the Access error in Run Time or in Access apps accessing ACCDE files has been gone, after the update install has been rolled back.
Addendum: Microsoft says, they are aware and the team is looking into that issue (some affected German blog reader had created tickets). On reddit.com there is this thread about that issue.
Addendum 1: See Fix for Access ACCDE/MDE bug (VBA library bug) for fixes.
Hello, we have a MS Access frontend application and after a windows office update it opens and after 1-2 seconds it closes. The update for MS Access 2013 is KB5002112 and for MS Access 2016 is KB5002121. If I uninstall these updates the application works fine. Does anybody know why this is happening?
Also we wanted to debug the application so we decided to open it as .mdb and we saw that the application had no problems. It is when we convert it to .mde the problem occurs.
In my case, it removed the reference to my accde library and therefore I've got the error messages.
If you need an uninstall script (example is for office 2016 32-bit):
REM removing KB5002112
:: get architeture
if %PROCESSOR_ARCHITECTURE%==x86 (
set reg_root=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
) else (
set reg_root=HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall
)
reg query "%reg_root%\{90160000-0011-0000-0000-0000000FF1CE}_Office16.PROPLUS_{C2D7565B-C52D-4D86-89CE-93C2236EF4A7}" /v UninstallString
if ERRORLEVEL 1 goto EndKB5002112
call start /wait msiexec.exe /package {90160000-0011-0000-0000-0000000FF1CE} /uninstall "{C2D7565B-C52D-4D86-89CE-93C2236EF4A7}" /qb
:EndKB5002112
Thank you for the uninstall script.
I tried to edit the script to work on office 2019 32 bits, but I can't manage to get it working.
Can u help me with the script for office 2019 32 bits?
Thanks in advance
Same problem here. Access 2013 closes right after opening mde file. Uninstall of KB 5002121 resolves it.
There is another workaround to solve that problem temporarily:
Replace the VBE7.dll unter «C:\Program Files (x86)\Microsoft Office\root\vfs\ProgramFilesCommonX86\Microsoft Shared\VBA\VBA7.1» or «C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX86\Microsoft Shared\VBA\VBA7.1» with a Version before Juli Office Update. After that the Access Application should be starting again without an error.
this is happening to two of my users as well, but KB5002121 is not showing as being installed to the device.