Uninstalled and re-installed again (as admin explicitly this time). Got rid of the messagebox looking for VBAOFF11.MSI, however, I am back to exactly where I was before I uninstalled and re-installed ACCPAC twice, and uninstalled and reinstalled Office 2013 once.

I go to run a macro, and nothing. Just a busy icon for a few seconds. Obviously something is running in the background, as I am unable to shut down ACCPAC for a few more seconds.

How can I tell what is going on? Thanks for any help you can offer.

I don't really have time to do an O/S reinstall.

Yup, I can open and edit them all from within ACCPAC.

I am pretty sure it is actually opening and trying to do something, it is just that nothing happens. No errors, just nothing.

They were working a month or so ago - so I have no idea what happened, unless it was Microsoft updating something to "help"

"Sage 300 ERP VBA has stopped working"

The macro works from other workstations. We have ACCPAC installed locally and running from each workstation, so it must be my workstation. I was hoping I could fix without an O/S reinstall, but it is not looking good.

Sage 300 ERP 2016

%1 error when I try to edit or run macros in Order Entry in Windows Server 2012R2 Terminal Server

You clicked on a shortcut that wasn't an AVB macro.

I think I see that 1% error when a macro has missing object references, most often after an upgrade. You may want to have the macro's developer take a look.

Sorry angel G, you are incorrrect.  Missing references in macros have completely different errors.  %1 is always caused when the file that's listed in the shortcut isn't a valid AVB file.  It can happen when people delete the original macro, and the user has an old shortcut.

In addition to Jay's answer about the macro file not being a valid macro file I have seen where a once valid macro file is turned into a non-valid macro file - usually with a file size around 2k.  Thus I always have a backup of any macro now (I should anyway but now I really ensure that).