Hello,
I'm deploying an application built on Access2003 that has to be used on pc
where Access is not installed.
I'm delivering Access runtime via Package Wizard.
I have also signed the code with a self-certificate.
When testing my application on a clean pc (i.e. windows xp SP2 without any
updates and with no office installed). Even if I install the certificate I
still have some warnings messages saying "do you want to block unsafe
expressions" popping up as soon as I launch my application.
Is there a way to get rid of these messages and having my application
running smoothly?
Thanks,
Rocco

rocco <(E-Mail Removed)> wrote:

>I'm deploying an application built on Access2003 that has to be used on pc
>where Access is not installed.
>I'm delivering Access runtime via Package Wizard.
>I have also signed the code with a self-certificate.
>When testing my application on a clean pc (i.e. windows xp SP2 without any
>updates and with no office installed). Even if I install the certificate I
>still have some warnings messages saying "do you want to block unsafe
>expressions" popping up as soon as I launch my application.

Macro Security Information for Access 2003
http://www.accessmvp.com/JConrad/acc...osecurity.html

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Thanks Tony,
actually I have managed the Package WIzard to edit the registry with thsi key
HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\engines\SandboxMode #0000000
and this is supposed to have setted the Jet sandboxmode to the lowest
security level possible.
But the warnings still pops out!
I think this has something to do with Access runtime somehow. But cannot
figure out how yet.
Rocco
"Tony Toews [MVP]" wrote:

> rocco <(E-Mail Removed)> wrote:
>
> >I'm deploying an application built on Access2003 that has to be used on pc
> >where Access is not installed.
> >I'm delivering Access runtime via Package Wizard.
> >I have also signed the code with a self-certificate.
> >When testing my application on a clean pc (i.e. windows xp SP2 without any
> >updates and with no office installed). Even if I install the certificate I
> >still have some warnings messages saying "do you want to block unsafe
> >expressions" popping up as soon as I launch my application.
>
> Macro Security Information for Access 2003
> http://www.accessmvp.com/JConrad/acc...osecurity.html
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>

rocco <(E-Mail Removed)> wrote:

>actually I have managed the Package WIzard to edit the registry with thsi key
>HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\engines\SandboxMode #0000000
>and this is supposed to have setted the Jet sandboxmode to the lowest
>security level possible.

Ah, visiting http://support.microsoft.com/default.aspx?kbid=294698 I
see what you mean.

I don't recall though if the unsafe expressions has to do with the
sandbox or the macro security. So you may be looking in the wrong
area.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

rocco <(E-Mail Removed)> wrote:

>actually I have managed the Package WIzard to edit the registry with thsi key
>HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\engines\SandboxMode #0000000
>and this is supposed to have setted the Jet sandboxmode to the lowest
>security level possible.

BTW I'd only ever use Name:SandBoxMode - Value:#00000002. The
likelihood of a malicious virus is far higher in a .doc or .xls file.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

You are right.. I have tried almost all the possible values and still the
messages comes out!
But... it has to do somethign with the sandboxMode since if I click 'yes'
(block unsafe exopressions) I can see that the registry has been modified
from 0 to 3.

So the message is related to that registry entry. I really start thinking it
has something to do with the runtime version of Access... I'll keep trying

"Tony Toews [MVP]" wrote:

> rocco <(E-Mail Removed)> wrote:
>
> >actually I have managed the Package WIzard to edit the registry with thsi key
> >HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\engines\SandboxMode #0000000
> >and this is supposed to have setted the Jet sandboxmode to the lowest
> >security level possible.
>
> BTW I'd only ever use Name:SandBoxMode - Value:#00000002. The
> likelihood of a malicious virus is far higher in a .doc or .xls file.
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>

rocco <(E-Mail Removed)> wrote:

>You are right.. I have tried almost all the possible values and still the
>messages comes out!
>But... it has to do somethign with the sandboxMode since if I click 'yes'
>(block unsafe exopressions) I can see that the registry has been modified
>from 0 to 3.
>
>So the message is related to that registry entry. I really start thinking it
>has something to do with the runtime version of Access... I'll keep trying

But I've done exactly the same thing myself except I set that value to
0002. Although I've done it in a different program and/or using
regedit.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Gosh... could then this be related to the lack of updates?
I'm installing my application on a clean XP Pro SP2 machine. WIndows has not
been updated and also access runtime has no updates. This is because usually
I prefer to test in the worst case scenario.

But what i happening is that I got two warning messages. The first is the
"block unsafe expression" And this is related to the sandboxmode. Then I
click NO and got the infamous Jet 4.0 SP 8 kind of thing. Which is really a
mistery since if I download the SP8 and try to instal it says I already have
it (thanks microsoft!!). If I install Office SP3 the second message wont show
up. But I still keep having the "block unsafe expressions" nicely popping
anytime I launch the application...
But throught the installation process I have changed the registry keys yu
were referrign to to:
HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\engines\SandboxMode #0000000
HKEY_LOCAL_MACHINE\Software\Microsoft\Access\Security #0000001

I cannot understand why it keeps showing up !!

I'm starting to thinking it is a matter of windows needing some update?
Boh... I'm lost...


"Tony Toews [MVP]" wrote:

> rocco <(E-Mail Removed)> wrote:
>
> >You are right.. I have tried almost all the possible values and still the
> >messages comes out!
> >But... it has to do somethign with the sandboxMode since if I click 'yes'
> >(block unsafe exopressions) I can see that the registry has been modified
> >from 0 to 3.
> >
> >So the message is related to that registry entry. I really start thinking it
> >has something to do with the runtime version of Access... I'll keep trying
>
> But I've done exactly the same thing myself except I set that value to
> 0002. Although I've done it in a different program and/or using
> regedit.
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>