Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Dynamics GP does not support VBA on Server 2019.
More information on this can be found here:
There are a few different tools to move away from VBA, some of which is held on that page. We also know the community has even more options, so you may be even more feedback on this thread.
I would suggest replacing your VBA code with GP Power Tools - Developer Tools module.
See why here: winthropdc.wordpress.com/.../
Deepak , you already have good responses just want to add that you can also hire freelancers to convert your vba code to dexterity. :-)
Have a client that is in the same boat in that they are in process of upgrading all their Servers to Windows 2019 and eventually upgrading GP as well. They have an extensive amount of VBA (that needs to be converted) and ran into the same GP Crashing issue anytime VBA code was touched on.
However, one of the client's techs found that replacing the VBE6.dll with a later version got them past the crashing issue. Albeit, this is a temporary workaround, as there is no guarantee that there won't be a Security Update that breaks things again (like the Office Suite security update that broke DOCX files that you so kindly posted about in another link). Not sure where they found the newer VBE6.DLL file, but the version information that was able to find is below:
Crashing version ==> 22.214.171.124
Working version ==> 126.96.36.199
Location C:\Program Files (x86)\Common Files\microsoft shared\VBA\VBA6
When searching the internet and other sites such as this, haven't found any mention of the temporary workaround mentioned above. Wondering what it is with Windows 2019 that stops GP/VBA combo from working? As noted, this temporary workaround resolves the GP crashing issue, but does not fix the GP/VBA/Outlook (Email) crashing issue, which requires an earlier version of Office, no VBA or switching from MAPI to Exchange.
So, wondering what your thoughts are on this?
Michael, can you provide the link from the customer for the 188.8.131.52 so it can be reviewed as a future consideration of what they did to get this working, thanks
As noted in my post "Not sure where they found the newer VBE6.DLL file". However, a Google Search points to 184.108.40.206 as being a security fix, which the client must have applied on one of their older Servers.
The following link (www.microsoft.com/.../details.aspx looks like it might do the job.
Regardless of this, do you know the underlying cause to why VBA stops working on Windows 2019?
Expect the above will only be a temporary workaround and that there is no guarantee that a new Windows 2019 security update won't break things again. And, yes, we need to get the client off of VBA sooner than later, but that is going to take quite a bit of time/resources due to the volume of modifications made using VBA through the years in their environment.
Glad to learn about this option as it buys us some time to communicate to the customer and get approval to re-develop these customizations.
Noting that the link on the page that I posted isn't working. What you want to look for is "www.microsoft.com/.../details.aspx. In case this link doesn't work either, then look for "Visual Basic for Applications Runtime Security Update", Knowledge Base Article KB974945.
I personally haven't tried downloading/installing the update, as my client that I was working with already had the DLL available, but can clearly see "Vbe6.dll 220.127.116.11" listed at the bottom of the KB article's Additional Information page.
We are definitely pushing to get all our clients off of VBA, but even with a workaround, you never know what might break it next! Just went through the process of changing DOCX to PDF to get around the new MS Security Update that breaks DOCX documents generated from GP Templates and switching from MAPI to Exchange to get around the Outlook/GP/VBA crashing issue.
I did notice the link placed a quote " after the address and had figured that out. However do thank you for the heads up.
Actually it is Michael, not Deepak (guess I should remember to sign my posts. Believe Deepak originated this BLOG chain. Had added my question to Justin, who also placed a response to this chain, wondering about what the true underlying cause is with the Windows 2019 O/S and GP/VBA.
Michael J. Nola.
Sorry for the confusion Michael
Indeed this one has us scratching our heads.
Whilst not using Dynamics, this thread helped me understand why a legacy Access application was suffering. Thanks!
I'm surprised nobody suggested using Visual Studio Tools for Microsoft Dynamics GP. I switched from VBA to that years ago as VB.Net is very similar to VBA and it made the coding transition easy. Also, Visual Studio Tools is much more capable than VBA.
We are currently on GP2018 and I am using Visual Studio 2019. Install the SDK located on the GP install media, in the Tools - SDK - VS Tools folder. I believe the Programmers Guide pdf gets installed as well so you can look it over. After installing Visual Studio 2019 you can go to Extensions and install the Microsoft Dynamics GP Item and Project Templates.
Business Applications communities