Trust VB projects setting Grayed out
 

I have one machine in my organization that has the "Trust Access to Visual
Basic Projects" grayed out. It won't let me change it, even when logged on
as a Domain Admin.

I have changed the Reg Key
HKLM/Software/Microsoft/Office/11/Excel/Security/AccessVBOM to 1. But it
is still grayed out.

I have searched KB but can't find an answer there.

Any suggestions. Is there a Local Machine Security Policy that is graying
this out???

Any help appreciated.

Dennis

Trust VB projects setting Grayed out
 

in tools/macros/visual basic editor

open in the vbe the tools/references menu
make sure that Microsoft visual bassic extensibilty 5.3 reference is checked

"dennis" wrote:

I have one machine in my organization that has the "Trust Access to Visual
Basic Projects" grayed out. It won't let me change it, even when logged on
as a Domain Admin.

I have changed the Reg Key
HKLM/Software/Microsoft/Office/11/Excel/Security/AccessVBOM to 1. But it
is still grayed out.

I have searched KB but can't find an answer there.

Any suggestions. Is there a Local Machine Security Policy that is graying
this out???

Any help appreciated.

Dennis

Trust VB projects setting Grayed out
 

Is VBA installed on that machine?

--
Regards,
Tom Ogilvy

"dennis" wrote in message
...
I have one machine in my organization that has the "Trust Access to Visual
Basic Projects" grayed out. It won't let me change it, even when logged
on
as a Domain Admin.

I have changed the Reg Key
HKLM/Software/Microsoft/Office/11/Excel/Security/AccessVBOM to 1. But it
is still grayed out.

I have searched KB but can't find an answer there.

Any suggestions. Is there a Local Machine Security Policy that is graying
this out???

Any help appreciated.

Dennis

Trust VB projects setting Grayed out
 

VBA is installed. I can create Macro's and edit them in the VBE. I don't
think I could do that if VBA was not installed, right?

I tried adding a reference to Visual Basic extensions 5.3 but that did no
good. I tried editing the Registry, setting AccessVBOM to 1. But that did
no good.

Any other suggestions.?

Dennis

"Tom Ogilvy" wrote in message
...
Is VBA installed on that machine?

--
Regards,
Tom Ogilvy

"dennis" wrote in message
...
I have one machine in my organization that has the "Trust Access to
Visual
Basic Projects" grayed out. It won't let me change it, even when logged
on
as a Domain Admin.

I have changed the Reg Key
HKLM/Software/Microsoft/Office/11/Excel/Security/AccessVBOM to 1. But
it
is still grayed out.

I have searched KB but can't find an answer there.

Any suggestions. Is there a Local Machine Security Policy that is
graying
this out???

Any help appreciated.

Dennis

Trust VB projects setting Grayed out
 

I don't use xl2003, so take this with a giant grain of salt.

From reading posts, it sounds like that option can be disabled (always
disabled??) via the user interface.

Did you try changing the registry with excel closed, then check to see if that
had any effect on your problem?

(I don't have any guess no matter what your response is--I just thought that
maybe checking via the user interface wasn't a sufficient check.)

dennis wrote:

VBA is installed. I can create Macro's and edit them in the VBE. I don't
think I could do that if VBA was not installed, right?

I tried adding a reference to Visual Basic extensions 5.3 but that did no
good. I tried editing the Registry, setting AccessVBOM to 1. But that did
no good.

Any other suggestions.?

Dennis

"Tom Ogilvy" wrote in message
...
Is VBA installed on that machine?

--
Regards,
Tom Ogilvy

"dennis" wrote in message
...
I have one machine in my organization that has the "Trust Access to
Visual
Basic Projects" grayed out. It won't let me change it, even when logged
on
as a Domain Admin.

I have changed the Reg Key
HKLM/Software/Microsoft/Office/11/Excel/Security/AccessVBOM to 1. But
it
is still grayed out.

I have searched KB but can't find an answer there.

Any suggestions. Is there a Local Machine Security Policy that is
graying
this out???

Any help appreciated.

Dennis





--

Dave Peterson

Trust VB projects setting Grayed out
 

I have changed the Reg Key
HKLM/Software/Microsoft/Office/11/Excel/Security/AccessVBOM to 1. But it
is still grayed out.

You have to delete the key. Then you can change the access setting through
the UI (which is written to the equivalent HKCU key).


--
Jim Rech
Excel MVP
"dennis" wrote in message
...
|I have one machine in my organization that has the "Trust Access to Visual
| Basic Projects" grayed out. It won't let me change it, even when logged
on
| as a Domain Admin.
|
| I have changed the Reg Key
| HKLM/Software/Microsoft/Office/11/Excel/Security/AccessVBOM to 1. But it
| is still grayed out.
|
| I have searched KB but can't find an answer there.
|
| Any suggestions. Is there a Local Machine Security Policy that is graying
| this out???
|
| Any help appreciated.
|
| Dennis
|
|

Trust VB projects setting Grayed out
 

OK, I found the answer. If anyone is interested. I had changed the key

HKLM\Software\Microsoft\Office\11\Excel\Security\A ccessVBOM to 1.

I expected this to make the UI check box a non-greyed-out option, but it
left it greyed out. But the box was not checked instead of unchecked.

So here is how it works. If you leave the key there and it is a zero the
option will be greyed out and unchecked. If you leave the key there and
make it a 1, the option will be greyed out but checked. If you remove the
key entirely the option will no longer be greyed out and the user can chose
to check it or not.

Hope that helps others.

Dennis

"dennis" wrote in message
...
I have one machine in my organization that has the "Trust Access to Visual
Basic Projects" grayed out. It won't let me change it, even when logged on
as a Domain Admin.

I have changed the Reg Key
HKLM/Software/Microsoft/Office/11/Excel/Security/AccessVBOM to 1. But it
is still grayed out.

I have searched KB but can't find an answer there.

Any suggestions. Is there a Local Machine Security Policy that is graying
this out???

Any help appreciated.

Dennis