1. You don't have to recompile AVB macros

2. 64-bit Excel won't work.

^ What Jay said. Also, check if there are any references missing in the VBA project from the workstations that don't work. Could be that an Office update changed significantly enough to change the dlls referenced in the macro.

Thank you!  There was something our macro vendor did when we upgraded to Sage 300 2021 because our macros wouldn't run. I thought they had either been recompiled or maybe re-saved?  Have you heard of a Sage 300 upgrade breaking macros before?

We still have Excel 32-bit on all five Sage 300 machines: the four that don't work and the one that does. 

Thank you.  I'm not familiar with how to edit macros.  Do you do that within Sage 300 or Excel?  or something else?

You can edit the macro by selecting the Edit button from the Macro grouping of icons on the main Sage screen. 

When the macro editor opens, go to Tools, References... If References is disabled then the macro has a password on it and you should contact your vendor.

On the References screen, look to see if any of the entries at the top of the list have the word "missing" next to any of them. You don't need to go down the list past the items that are checked. It's a long list and the relevant items on the list are moved to the top.

If there are items with "missing" next to them, then the next step is to resolve that.

You haven't indicated if your macro contains a Sage screen within it. If that's the case then that's why after each upgrade to Sage you need to update the macro. You can also be affected if you install a product update for your existing version.

Anti-virus software will sometimes flag a macro or files that a macro needs to run as problematic. Sometimes for a valid reason, sometimes it's a false positive. If you have the option, you can try to disable your anti-virus for a few moments and try to run the macro.

Thank you!  I wasn't able to get the macro to open in VBA. I did some searching online and found a post about VBA either missing or being the wrong version/architecture.  The post included a download of the VBA 7.1 x86 installer.   I downloaded and installed VBA 7.1 x86 and now the macro opens and runs successfully.  

We are running Office 2019 x86 so. Any idea why I needed to install VBA 7.1 x86? I thought VBA came with Office and matched the version/architecture.   

It's a common problem, Office doesn't always install VBA.  And we do Office repairs regularly when there's an auto-update over the weekend and it breaks Sage Intelligence.

Thanks.  Is there a specific option you have to select when installing Office 2019 from scratch? We use an Office Configuration File (.xml) when we install Office 2019. It includes which apps get installed (e.g Word, Excel) and which apps are excluded (e.g. Access). Also includes whether to install the x86 or x64 version,  the product key, etc.  I don't remember VBA being a choice but plan to go back and look.