News and Announcements icon

Dynamics 365 CommunityForums Microsoft Dynamics GP (Archived) Adobe 11 conflict with...

Microsoft Dynamics GP (Archived)

Adobe 11 conflict with VBA in Dynamics 2010

(0) Share

Report

Report

Posted on by Lisa Raynor

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

All responses Img

All responses (2)

Answers Img

Answers (2)

Verified answer

Mariano Gomez 26,225 on at

Like (0)

Report

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 Microsoft Employee on at

Like (0)

Report

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

Helpful resources

Quick Links

Leaderboard

#1

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

#2

Martin Dráb 230,214 Most Valuable Professional

#3

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans