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