VBA Not Initialized Error

Microsoft Dynamics GPI seem to have spent a lot of time over the last few months building demo machines; I’m not sure I have, but it seems that way with the rapid release schedule that Microsoft Dynamics GP was on.

I’ve seen the below error message a few times when trying to import VBA customisations and have had to do an investigation each time as to what the problem was, before realising it was exactly the same problem again:

Microsoft Dynamics GP: VBA cannot be initialized. Cannot import this package because it contains VBA components.

Microsoft Dynamics GP

VBA cannot be initialized. Cannot import this package because it contains VBA components.

This post, is in an attempt to remind myself of what the error is without having to investigate.

The issue each time has been that the registration keys for Microsoft Dynamics GP have not been entered; VBA customisations cannot be imported if the Customisation Site Licence is not registered.

Once the keys are entered, the error goes away and the VBA customisations can be imported without further issue.

What should we write about next?

Your Name (required) -
Your Email (required) -

(Visited 55 times, 1 visits today)

One thought on “VBA Not Initialized Error

Leave a Reply

Your email address will not be published. Required fields are marked *