After communicating with the Office team it sounds like the redistributable version of VBA that is packaged with Microsoft Dynamics GP has reached end-of-life, which means it is no longer tested for compatibility with the monthly Office 365 releases. Such a compatibility issue was found in build 1811 and later versions of Office 365. It does not appear that there is a newer VBA redistributable that we could package with the Microsoft Dynamics GP installer that would address this issue. Since there are likely ISV products and customizations that require VBA and we want to maintain their functionality we’ve decided that the current VBA build will still be packaged with future installation media.
After weighing our options to move forward we’ve identified three workarounds to consider that you can read about in Lucas' blog post, Microsoft Dynamics GP and VBA: Future Considerations.
After further testing, we have narrowed the issue to Any Custom VBA code installed on Dynamics GP. If you remove all VBA code, this will remove the issue with GP Crashing when emailing. See below for how to check if you have VBA code installed. We cannot guarantee that removing the VBA won't have any side effects. You will have to know what your VBA contains.
We have seen a few cases around the topic of Dynamics GP crashing or closing when accessing any email/outlook functionality for any Microsoft Office version newer than 1810.
Affected GP Versions: 2013, 2013R2, 2015, 2015R2, 2016, 2016R2, 2018, 2018R2
You have 3 options to resolve. You should only have to apply 1 of these options, not all of them.
(We cannot guarantee that removing the VBA won't have any side effects. You will have to know what your VBA contains.)
File-> Office Account-> Update Options-> Disable Updates
** We do not know if the next release of Office will fix this issue. ** Based on current cadence of releases, we estimate the next release of Office will be in January.** At that time, I would recommend testing on one machine to see if resolves the issue.
Thank you, we found rolling back the patch worked and were hoping a fix was on the way. For GP 2010 users - We use GP 2010 and some users have office 2016. I know GP 2010 and office 2016 is not supported, but we have a lot of custom and cannot update GP yet. The "rename GP code folder" option fixes the problem until I add our VBA files back or create new VBA files. Rolling back the patch does work.
Thank you sir! Rolling back Office365 standard use to 16.0.11001.20074 fixed this issue for us, just waiting on the Office fix now...
Has anyone heard if the January Office release is available and can confirm GP no longer as an as the issue after the Office update?