As a follow on from yesterday’s article on how different languages can be used to drive the Microsoft Dynamics GP user interface, this article discusses the need to move away from the old Visual Basic for Applications (VBA) way of thinking. If you missed yesterday’s article, here is the link.
Now that VBA is “End of Life” and many sites are starting to use GP Power Tools – Developer Tools module to replace the VBA business logic with GP Power Tools triggers and scripts. However some developers are still trying to write code as though they were still limited by VBA rather than leveraging the more powerful capabilities of GP Power Tools and Dexterity.
In recent times many Microsoft Dynamics GP sites have been having issues with VBA (Visual Basic for Applications). Especially with Microsoft Office Updates breaking functionality and incompatibilities with later Windows Server releases.
There have been compatibility issues reported with sending emails via Outlook and more recently issues with VBA on Windows Server 2019.
As a follow on to the recent post : #GPPT Why every GP site needs GP Power Tools – Developer Tools, this article explains the benefits of replacing your VBA (Visual Studio for Applications) and VSTools (Visual Studio Tools for Microsoft Dynamics GP) customizations with GP Power Tools.
It has been prompted by the issues seen because the redistributable version of VBA that is packaged with Microsoft Dynamics GP has reached end-of-life as explained in the following article from the Microsoft Dynamics GP Support and Services team:
Hey Developers… Are you attending the GPUG Summit 2017 conference in Nashville, Tennessee in October? If so, this article is to let you know about Microsoft Dynamics GP related Developer content at the conference.
I asked why there was not much content for developers at GPUG Summit and I was told that there are not many developers in attendance. I disagreed and requested a session for Developers, which Bob McAdam promptly organised … thanks Bob. 🙂
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
The following Report Writer and VBA example demonstrates how data from any SQL table can pulled into a report regardless of the product the table is related to. This technique can also be used when it is not possible to create the table relationship needed to add the report in the Report Writer. It works as long as you can create a query that will uniquely select the data you need based on the data on the report or from the already linked tables.