Skip to main content

Notifications

Microsoft Dynamics GP (Archived)

Adobe 11 conflict with VBA in Dynamics 2010

Posted on by

Hello

Our customer has VBA mods on a project window (billing entry) and since installing Adobe 11 they get the following messages.

Opening window

Microsoft Visual Basic

Run time error 91

Object variable with block variable not set

On window

An unexpected error has occurred in procedure SetSQLLogins

Microsoft OLE DB Provider for ODBC Drivers

Error-2147a67259

[Microsoft][ODBC Driver manager] Data source name nor found and no default driver specified

On window

An unexpected error occurred in procedure Get_GP_Info

Project Accounting

Error 429

Active X component can't find object.

Has anyone encountered anything similar? Or have any suggestions on how to troubleshoot this?

*This post is locked for comments

  • Verified answer
    Mariano Gomez Profile Picture
    Mariano Gomez 26,225 on at
    RE: Adobe 11 conflict with VBA in Dynamics 2010

    You posted on the partner forum too, so just in case here's my reply:

    The only thing I can think of is your VBA dlls got corrupted when you installed Adobe Acrobat 11. As such you probably need to reinstall these, as follow:

    VBA Runtime 6.0 -  support.microsoft.com/.../290887

    VBA Runtime 6.5 -  www.microsoft.com/.../details.aspx

    You can always run the msi from the VBA folder on the GP media.

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Adobe 11 conflict with VBA in Dynamics 2010

    Hi Lisa,

    I don't have a straight answer for this as I have not seen issues with Adobe before.  I have seen other issue where windows updates have broken VBA and these are the steps that I used to resolve the issue.

    1. Go into VBA and go to Tools> References.  Write down all the references that are being used.

    2. Export all your VBA customizations via Tools > Customization > Customization Maintenance (in GP).

    3. Log out of GP 

    4. Delete or rename the Dynamics.vba and any other .vba file that may be in use.

    5. Log into GP.

    6. Import your VBA customizations via Customization Maintenance.

    7. Go into VBA and verify that all the references you need are checked.

    This basically resets your VBA environment.

     I wish I had something more succinct for you...  Let me know if this helps!

    Terry Blaser

    Terry@dynbuilders.com

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

New! Quick response templatesâš¡

Save time with the new custom templates!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,228 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,056 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans