Microsoft Dynamics GP, VBA and Windows Server 2019/2022

Bill Cat

Bill Cat likes VBA too.

This has been a constant battle royale for me: what to do with VBA customizations in Microsoft Dynamics GP since they don’t work with Windows Server 2019/2022? I’ve been slow walking any kind of solution since Windows Server 2016 is still in support (until now) — so it just wasn’t a worry.

Well, there is a solution for this besides another piece of software or rewriting everything in Dexterity.

The GP support team has released more guidance on the VBA customizations compatibility with Windows Server 2019/2022.

Here’s the original post in the Dynamics GP community forum:

Microsoft Dynamics GP and VBA: Future Considerations

Here’s an update about that post in mid-2022:

VBA causing issues in Dynamics GP? Here’s a possible solution.

And here’s the link to the download for the VBA security fix (from the article above):

Visual Basic for Applications Runtime Security Update

In the supported operating systems list, it only shows Windows Server 2008, Windows XP, Windows 2000, Windows Server 2003, Windows Server 2008 R2, Windows 7, Windows Vista. This update will run on Windows Server 2019/2022, too.

Directly from Microsoft, they state they continue to “support” VBA in all the latest operating systems:

Support Statement for Visual Basic 6.0 on Windows

On a fully patched Windows Server 2019 system running GP 18.4.1461 (and higher) with the VBA security update installed, all VBA customizations work. GP does not crash.

HOORAY!

As someone who has done lots and lots of VBA work over the years, all of this news is a bit of a welcome relief. The sky is not falling where you have to change out all your VBA to something else NOW NOW NOW. Don’t get me wrong, you’re going to have to do it sometime, but as long as Microsoft is still claiming “it just works” support with all the latest operating systems, it doesn’t have to be right now.

If you’re running the web client, that’s another story — but seriously? The web client?

Leave a Comment

Your email address will not be published. Required fields are marked *