VBA causing issues in Dynamics GP? Here's a possible solution.
Hello Dynamics GP Community!
As we published on this site a couple years ago, the Dynamics GP application has experienced some compatibility issues around VBA due to updates on the stack of technology we rely on:
(99+) Microsoft Dynamics GP and VBA: Future Considerations - Microsoft Dynamics GP Community
Since this conflict with MAPI e-mailing as well as Windows Server 2019 first came to light our intrepid Dynamics GP community has come forward with several workarounds. One that I would like to present to you today is an updated version of the Visual Basic for Application runtime, which can be found at the following page:
All you need to do is download this and install it on any machine where you have Dynamics GP installed and also use VBA. In most cases we've had positive results with this.
Hope this helps those of you in the community who have been sticking with their VBA customizations!
Comments
-
Do you have huge amount of code written in VBA and Modifier? Upgrading GP and your code not working any more? If yes! Get quote to transfer your existing functionalities and logic to Dynamics GP Native programming tool Dexterity, in a very reasonable price. Email:DexterityDeveloper@gmail.com keptonworking.blogspot.com/.../get-quote.html
-
To address some of the questions, this isn't really meant as a statement of official support. The Dynamics GP installer is still going to lay down the VBA redistributable that has issues with Windows Server 2019 and certain versions of Office. This hasn't gone through any full regression testing from our Product Team, so it's really more of a workaround that will hopefully address issues in most customer environments. Despite what the System Requirements on the VBA update state we've seen positive results with Windows Server 2019, but we cannot vouch for any compatibility on the VBA side. Hopefully when we support Windows Server 2022 we don't see similar issues being reported.
-
Please be aware that GP Power Tools is an excellent method to replace VBA. Once the code is written there are no additional deployment steps or upgrade steps. Maintenance is simple as the code is stored centrally in SQL tables. The triggering and scripting is more powerful and stable than VBA as you have access to all the underlying scripts and table buffers as well as the user interface. You also have the ability to use Dexterity, SQL, C# and VB.Net to write code (even though Dexterity is the primary language). winthropdc.wordpress.com/.../
-
The Office team released a buggy VBA module. Then the GP team said "oh, I guess we don't support VBA anymore". Then the Office team released a fix for the bug. Can the GP team please officially designate VBA as fully supported again (including in Windows Server 2019 and newer)?
-
Thanks Lucas, thanks for this update, I do hope this is the rainbow that leads to the pot of gold that many of us were looking for. I want to confirm that you're saying that this application that says supported operating system versions as noted below might allow VBA to function on a Windows Server 2019 machine? Windows Server 2008, Windows XP, Windows 2000, Windows Server 2003, Windows Server 2008 R2, Windows 7, Windows Vista
*This post is locked for comments