It's been quite a while since I've had to import package files into Dynamics GP, so when I got this error today when trying to import a large package file into GP 2013, it puzzled me for a few minutes.
Error: "VBA cannot be initialized. Cannot import this package because it contains VBA components."
If you search for this error, you will likely come across a Microsoft KB article saying that this error means that your VBA install is damaged and you have to fix it. Um, no, I don't think that's the issue, since I have three GP installs on this server, and all of the VBA customizations work fine, and I can import packages into those other GP installs.
So something else was up.
Thanks to the prolific Dynamics GP Community Forum, I found this thread from 2010 where a clever user recommended checking to see if Modifier was registered in GP. Hmmmm.
Sure enough, this was a new GP 2013 R2 install, and I hadn't yet entered reg keys. Once I entered the license keys and saved them, the package imported fine.
What a useless error message.