LinkBack Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
  #3   Report Post  
Posted to microsoft.public.excel.programming
external usenet poster
 
Posts: 989
Default Excel 2003 - Error Running Macro

Thanks keepITcool.

We were able to check the box ""Trust Access to Visual Basic Project" in
xl2003, so your comment is about it being greyed-out was surprising. But
maybe you can check it all you want but if it does not change in the registry
then ... it won't run.

Sorry for the basic question, but How does one check the registry? (Assume
you are taking me through the process step by step).

I have not been able to check the references yet. It is on a different
machine and I don't know the password. I will check this however.

Thank you for your help.





"keepITcool" wrote:


that's strange.

In my experience that message ONLY pops when AccessVBOM
is disabled (UNchecked).

Also afaik you cannot change that checkbox in xl2003...
it's visible but greyed out and you must change it via registry.

Just to be on the safe side:
check that the registry setting is entirely correct:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\ Excel\Security
there should be a

Type : REG_DWORD
Name : AccessVBOM
Value: 0x1 (Enable/Allow)


(Note that in xl2002 it was located in HKEY_CURRENT_USER)


Other things to check...
xl2003 throws oddly placed errors when
References are checked but missing/invalid.

Verify in Tools References that none of the references
for the project are marked as [ISMISSING]

hth.. but somehow i fear it wont.


--
keepITcool
| www.XLsupport.com | keepITcool chello nl | amsterdam


Mark wrote :

A program that runs in Excel 2002 will not in Excel 2003. The Excel
2003 is on an entirely different machine.

It gets hung-up on the "For Each" line in the following code:

Dim vbModule As Object
For Each vbModule In appWB.ActiveWorkbook.VBProject.VBComponents
If vbModule.Type = 1 Then ' "1" is a module
appWB.ActiveWorkbook.VBProject.VBComponents.Remove
vbModule End If
Next vbModule

The error reads: "Run Time Error '1004' Programmatic access to Visual
Basic Project is not trusted".

We have checked the "Trust Access to Visual Basic Project" check box
in the Tools/Macro/Security/Trusted Sources window.

Any ideas?

Thank you, Mark


 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
I tried to get around the problem of the pivot table field settingdefaulting to Count instead of Sum by running a macro of change the settingfrom Count to Sum. However, when I tried to run the Macro, I got error messageof run time error 1004, unable Enda80 Excel Worksheet Functions 1 May 3rd 08 02:35 PM
I tried to get around the problem of the pivot table field settingdefaulting to Count instead of Sum by running a macro of change the settingfrom Count to Sum. However, when I tried to run the Macro, I got error messageof run time error 1004, unable Enda80 Excel Discussion (Misc queries) 1 May 3rd 08 10:52 AM
Excel 2003 Macro Error - Runtime error 1004 Cow Excel Discussion (Misc queries) 2 June 7th 05 01:40 PM
Error when running macro in Excel Raphael Saddy Excel Programming 4 April 12th 04 09:09 PM
KERNEL32.DLL error after running EXCEL Macro Dan[_16_] Excel Programming 0 July 23rd 03 08:15 PM


All times are GMT +1. The time now is 11:34 PM.

Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 ExcelBanter.
The comments are property of their posters.
 

About Us

"It's about Microsoft Excel"