web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

VBA Cannot be initialized. Cannot Import this package because it contains VBA components

(0) ShareShare
ReportReport
Posted on by 725

Hi All,

I am experiencing an issue with one of our customers. They have a new client machine running windows 7 and have installed GP9. Everything is working ok expect the VBA modifications on one of the reports is not being recognised. When I try and import the VBA report package file I recieve the following error message:

"VBA Cannot be initialized. Cannot Import this package because it contains VBA components"

I have tried serveral things to try and overcome this but none have worked so far. I have tried the following as a result of my research:

- Repaired Microsoft Office

- Run GP as an administrator and then tried to import the package file

- Ensured all users have read and write access to the dynamics folder

I understand that GP9 is no longer supported but if anyone could offer any advice or guidance it would be much appreciated. The only other thing I can think of doing is to uninstall and reinstall to hope VBA components are installed this time.

Kind regards,

Nia.

*This post is locked for comments

I have the same question (0)
  • Tim Foster Profile Picture
    8,515 on at

    Where and how was the package developed? It does import fine on other machines?

    Tim

  • Nia Stockwell Profile Picture
    725 on at

    Hi Tim,

    The package was exported from a working client. It can be imported successfully on other machines.

    Kind regards,

    Nia

  • Verified answer
    Dan Liebl Profile Picture
    7,320 on at

    Does the package include the modConn and retrieve globals components for the package?   These need to be included in each workstation.    I can't give the technical explanation of all of the different components that need to be included, but without those, you will run into situations such as the one you are facing.

    Dan Liebl, CMA CPIM | Senior Consultant | OTT,Inc | DLiebl@OTT-inc.com

  • Community Member Profile Picture
    on at

    I have the same issue importing an older package (developed for GP9) in GP2013 on a Windows 7 pc.  I was able to import the package on all of my other workstations.  The only difference with this pc is that it has Office 2010.  All other workstations has either xp or win7 and Office 2003.  

    Did you find a solution ?  Thanks in advance

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans