Hi Vicki,

This may be unrelated, but we recently noticed a Microsoft Office 2019 installer (which was run by a third party after Sage 300 was installed) had uninstalled the Visual Basic for Applications and Microsoft Access database engine 2016 programs that were installed along with Sage 300.

The Windows Application logs (Event Viewer > Windows Logs > Application > Filter Current Logs > Event sources > MsiInstaller > OK) clearly showed the date and time that these programs were uninstalled, which helped with explaining what was going on to the client. Our only option at the time was to perform a complete reinstall (not a big deal for a new build but would have been a pain in production).

Sage (thanks Dawie Nel) has since provided an installer (Solution ID: 116895) for Visual Basic for Applications, and a link to the Microsoft Access Database Engine 2016 Redistributable.

If you manage to get macros working again by running the VBA installer, or some other solution, I'd be keen to hear about it (or any other insights/links you may have) as these issues can be a pain to diagnose and explain.

Also, not sure if you've come across this link which is specific to M365's behaviour regarding blocking VBA from external sources.