Excel 2007: error '1004' Programmatic access is NOT trusted

I'm running some code on XP Excel 2007 and receive the error below

Runtime error '1004'
Programmatic access to Visual Basic Project is not trusted.

I found a solution to this issue - used it and it DOES solve the issue - no more error and my program executes correctly on the XP Excel 2007 system where it previously failed
(NOTE: This same code works correctly on my XP Excel 2000 system)
------------------------------------------------------------------------------------------------------------
From the MS KB Article #812969

http://support.microsoft.com/kb/813969

States:
When you run code that uses the Microsoft Visual Basic for Applications Extensibility 5.3

Library, you may receive the following error message:

Run-time error '1004': Programmatic access to the Visual Basic Project is not trusted

Solution:
Excel 2007
Click the Microsoft Office Button, and then click Excel Options.
Click Trust Center.
Click Trust Center Settings.
Click Macro Settings.
Click to select the Trust access to the VBA project object model check box.
Click OK to close the Excel Options dialog box.

Excel 2003
On the Tools menu, point to Macro, and then click Security.
In the Security dialog box, click the Trusted Sources tab.
Select the Trust access to Visual Basic Project check box.
Click OK.
------------------------------------------------------------------------------------------------------------

Is there a way for me to turn this setting ON programatically when I need it?

Thanks,


BTW: A better solution would be - get the setting that the user has, set it to what I need to not CRASH, then return back to the USERS setting after I'm done.

Thanks for the response.....

1). Though I can't see the answer (the thread) w/o being a "user" on that forum
I guess I could get a 30 day trial to view the answer, but I'm NOT giving my credit card and picking a plan for the answer to ONE of my questions.

2). and I did say the following in my original post...
BTW: A better solution would be - get the setting that the user has, set it to what I need to not CRASH, then return back to the USERS setting after I'm done.
so I would change the setting to get the functionality to work, then change it back

3). The other solution would be for me to tell the user to go change their setting for this functionality to work.... Not an elegant solution for the user, if they can actually find their way there and get the setting correct.

Nope - you didn't miss it and it really doesn't matter. IMHO

I get the error on Excel 07 and not Excel 2000, Hence it points the issue to an Excel 07 specific area (or feature) which is described in the initial post.

The fix is also evident and works, just manual. I'd just like to make this easy on the user vs telling them "In order to make my program that works on your machine actually work... Follow these steps or Excel will CRASH". Not very user friendly......

Anyone else - any way to perform those setting programatically????

Thanks for the recent replies - tonyh & rimperstomper, I'll try the suggestions.

And look for additional ways to make this work....

Thanks,

The reason I'm using "Microsoft Visual Basic for Applications Extensibility 5.3" and thus getting errors on Excel 2003 & 2007 is because I'm retrieving, removing and copying module names from an Excel file. I update from a source file into a destination file for upgrades/updates....

Is there anyway to do these operations without the VBIDE.VBProject reference and using this extension?

If not, I'll have to resort to the following....... I'll detect the setting (and the impending error) using the suggestions above and some "ACCESSVBOM" code I found, and either popup instructions or redirect them to the instructions on my website. Allow the user to make the registry change to successfully update/upgrade their product.....


Thanks,

I decided to do direct updates of the files vs updating the modules within the file and using the "Microsoft Visual Basic for Applications Extensibility 5.3" and therefore getting the "Trusted App" issue on Excel 03/07.

I could have detected the setting that would cause the issue, and either explain what needed to be performed to avoid the issue or pointed the user to a web site that explained what to do. This is a hassle that I just didn't want the user to go through....

Thanks for your help & suggestions.