> If you found that branch in the registry, I wouldn't delete it.
>
[quoted text clipped - 48 lines]
>> >
>> > Dave Peterson
The problem is that you should be able to make that change through the user
interface and excel should remember it. It's quite unusual that you can't do
this.
I _think_ that in all the posts that describe this problem, it usually comes
down to a permissions setting that the IT staff put on the users. That's why I
think it's not excel's problem, it's you're IT staff's problem.
> Thanks Dave for suggestion!
> This allows to set another than the low level, doesn't it? How to make Excel
[quoted text clipped - 56 lines]
> >
> > Dave Peterson

Signature
Dave Peterson
Dave Peterson - 26 Apr 2008 23:05 GMT
... it's _your_ IT staff's problem.
(stupid fingers!)
> The problem is that you should be able to make that change through the user
> interface and excel should remember it. It's quite unusual that you can't do
[quoted text clipped - 68 lines]
>
> Dave Peterson

Signature
Dave Peterson
Dima - 27 Apr 2008 06:08 GMT
Thanks Dave for replying!
Our IT staff says that they did not put any LOCAL restrictions on me. I have
full LOCAL administrator rights.
Sincerely.
> The problem is that you should be able to make that change through the
> user
[quoted text clipped - 75 lines]
>> >
>> > Dave Peterson
Dave Peterson - 27 Apr 2008 11:40 GMT
I don't have another guess.
Good luck. If you find the solution, please post back so that google has it.
> Thanks Dave for replying!
> Our IT staff says that they did not put any LOCAL restrictions on me. I have
[quoted text clipped - 83 lines]
> >
> > Dave Peterson

Signature
Dave Peterson
Jim Rech - 28 Apr 2008 00:32 GMT
Dave-
This may not be it for the OP but if the "Level" entry exists under HKLM:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Excel\Security
Then it is sticky. It allows you to change it for the current session but
the HKLM setting remains the default. I have no idea how the HKLM gets set
initially though.

Signature
Jim
>I don't have another guess.
>
[quoted text clipped - 93 lines]
>> >
>> > Dave Peterson
Dave Peterson - 28 Apr 2008 02:09 GMT
I hope the OP is still hanging around.
I remember other posts that describe the same stickyness problem with the "trust
access to Visual Basic project" (IIRC).
Here's hoping that this fixes it.
> Dave-
>
[quoted text clipped - 109 lines]
> >
> > Dave Peterson

Signature
Dave Peterson
Dima - 28 Apr 2008 18:12 GMT
Thanks Jim for replying!
Should I delete the "Level" entry under
HKLM\SOFTWARE\Microsoft\Office\11.0\Excel\Security ?
How is OP interpreted?
Sincerely.
>I hope the OP is still hanging around.
>
[quoted text clipped - 131 lines]
>> >
>> > Dave Peterson
Dave Peterson - 28 Apr 2008 18:42 GMT
OP = Original Poster.
For me, I don't have this key.
You may want to rename it (SecurityX, maybe). Then test it out.
If that fixes the problem, I'd delete the key.
> Thanks Jim for replying!
> Should I delete the "Level" entry under
[quoted text clipped - 140 lines]
> >
> > Dave Peterson

Signature
Dave Peterson
Dima - 29 Apr 2008 19:40 GMT
Deleting the Level entry resolved the problem!
Thanks Dave!
> OP = Original Poster.
>
[quoted text clipped - 158 lines]
>> >
>> > Dave Peterson
Dave Peterson - 29 Apr 2008 19:45 GMT
Thanks for posting back.
I'm sure Jim appreciates the feedback, too.
> Deleting the Level entry resolved the problem!
> Thanks Dave!
[quoted text clipped - 164 lines]
> >
> > Dave Peterson

Signature
Dave Peterson