Monday, December 6, 2010

VBA6.DLL File Not Found Error with Dynamics GP 2010 and Office 2010

I am helping a client upgrade from GP 9 to GP 2010, and as part of the upgrade, we are reviewing and documenting dozens of GP customizations that they have had in place for years, many of which are no longer used.

While I was reviewing the Modifier & VBA customizations on the test server, I received an error when I tried to open one of the modified windows.

"File not found: VBA6.DLL"

Thankfully, Vaidy Mohan had bumped into this error back in August and posted to the partner forum.  Beth Gardner with Dynamics support then graciously posted an entry on the Developing for Dynamics GP Blog explaining the issue and providing a resolution.

It appears that the issue is due to changes that are made by the Office 2010 installation routine that break the Dynamics GP VBA file references in the registry.

It appears that it was originally thought that this might be specific to 64-bit Windows environments, but Beth followed up last month with a new post explaining how it affects 32-bit Windows as well.

The solution looks a bit intimidating, but is just a relatively simple registry update, although Beth reports that some customers had to perform some additional steps to resolve the issue.

I thought I would write a post under the headline of Office 2010, as that seems to be the culprit.

Steve Endow is a Dynamics GP Certified Trainer and Dynamics GP Certified Professional.  He is also the owner of Precipio Services, which provides Dynamics GP integrations, customizations, and automation solutions.

No comments: