Security warnings

[Salad]

On one computer I am getting the message "This file may not be safe if
it contains code that was intended to harm your computer. Open It?" and
on my computer I didn't get that message when I opened the same app.
This was due to me setting security level low on my computer but not
setting it on the other computer.

On the computer getting the error message I was also getting "Unsafe
Expressions Not Blocked" error messages. I think, but am not 100% sure,
this was stopped when I got SP2 for Access. I read that you get this
message if Jet 4.0 SP8 and Sandbox mode has not been enabled.

Does the Access 2003 SP2 contain the Jet 4.0 required updates? Where do
you find the Jet/SP information in A2003? I checked in the About area
in Help but didn't spot anything in the main dialog or under SystemInfo.

Do most people set their security level to low? If so, is there a real
purpose to these security warnings? Or are these messages simply
presented to cover Microsofts butt? Or are there real security threats
out there?

If there are security threats lurking in apps, it seems it would make
sense to set security to low for the apps you work with and trust. For
new apps the user should be asked if it is trusted or not. Once you
determine it is trusted, then set it low. Right now it seems if you set
the security level low it is set low for all apps...all or nothing.

[Allen Browne]

Yes: set the macro security to Low in Access 2003.
This makes A2003 behave the same as previous versions.

For Access 2007, place your databases in a trusted folder.
Then tell Access this location is safe, via:
Office Button | Access Options | Trust Center | Trust Center Settings

Most users never accept databases from unknown sources. If you do, place
them in an untrusted folder, open them in a virtual machine, or change the
security level while opening those databases.

For most of us, this A2003 security warning is about as useful as forcing
bicycle riders to wear seatbelts.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Salad" <oi*@vinegar.co mwrote in message
news:13******** *****@corp.supe rnews.com...

On one computer I am getting the message "This file may not be safe if it
contains code that was intended to harm your computer. Open It?" and on
my computer I didn't get that message when I opened the same app. This was
due to me setting security level low on my computer but not setting it on
the other computer.

On the computer getting the error message I was also getting "Unsafe
Expressions Not Blocked" error messages. I think, but am not 100% sure,
this was stopped when I got SP2 for Access. I read that you get this
message if Jet 4.0 SP8 and Sandbox mode has not been enabled.

Does the Access 2003 SP2 contain the Jet 4.0 required updates? Where do
you find the Jet/SP information in A2003? I checked in the About area in
Help but didn't spot anything in the main dialog or under SystemInfo.

Do most people set their security level to low? If so, is there a real
purpose to these security warnings? Or are these messages simply
presented to cover Microsofts butt? Or are there real security threats
out there?

If there are security threats lurking in apps, it seems it would make
sense to set security to low for the apps you work with and trust. For
new apps the user should be asked if it is trusted or not. Once you
determine it is trusted, then set it low. Right now it seems if you set
the security level low it is set low for all apps...all or nothing.

[Salad]

Allen Browne wrote:

Yes: set the macro security to Low in Access 2003.
This makes A2003 behave the same as previous versions.

Hi Allen. Thanks for the advice.

Next step for me is to put that menu option for runtime users.

For Access 2007, place your databases in a trusted folder.
Then tell Access this location is safe, via:
Office Button | Access Options | Trust Center | Trust Center Settings

Most users never accept databases from unknown sources. If you do, place
them in an untrusted folder, open them in a virtual machine, or change
the security level while opening those databases.

For most of us, this A2003 security warning is about as useful as
forcing bicycle riders to wear seatbelts.

A funny concept.

[Stuart McCall]

For most of us, this A2003 security warning is about as useful as forcing

bicycle riders to wear seatbelts.

Aye but it lets Microsoft unload responsibility for security onto the user.
<Hack, spit>

(nicely put, BTW)