KB5002121 breaks MS Access runtime applications

Hi,

we found difference betwwen 32bit and 64bit Office version:

accdE compiled with old version does not show the error when opened in recent version (with error).

Seen in Office Professional Plus Version 16.0.5278.1000 64 bit; KB5002112 (64bit) is installed.

Anyone can confirm this behaviour?

I have had a 2587 error when I try to output a report to html (or anything other than PDF) and am wondering if this has to do with the recent Access update. Does anyone know if output to HTML is affected by this current issue? It worked fine until a few days ago, basically quit working about the same time Access updated. Right now no report can be outputted to text, html, RTF... etc.

Error msg: the visual basic code you entered contains a syntax error or the output procedures are not available

Thanks

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?

SEVERAL users of our Access RT application experiencing the same problems.

Have spent all day fielding customer support emails and remote support to help uninstall and reinstall Office. ALL versions of Access needed to be uninstalled/reinstalled - RT, Full or 365.

Yes the update looks to have caused the issue, not the first time this has happened. Recompiling the same database on the updated version appears to fix the issue. On a previous issue I rolled back the update that caused the issue. Hope this helps.

Hi Kevin,

we don't export HTML or pdf directly. We export and automate to Excel including Pivot Charts and to Word.
No failure has been noted here which could be related to kb5002112 issue.

Wolfram

Hi anselyRayan,

this soltution we are doing actually and 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.