Re: Access 2003 security warnings
- From: "Richard Harison" <noway@xxxxxxxxxxx>
- Date: Wed, 6 Dec 2006 19:39:42 -0500
Thank you Joan!
I will forward your recommendation. Your logic is well taken--2002 is then
theoretically "wide open " to the attack you describe as virtually
non-existent.
Since I do not run 2003, perhaps you could tell me where the macro security
level set is. Is it in Tools>Options>Security Tab like Excel? Or is it in
Tools>Security, where all the permission stuff is?
Thanks again!
--
All the Best,
Richard Harison
"Joan Wild" <jwild@xxxxxxxxxxxxxxxx> wrote in message
news:OWttUuYGHHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
Richard Harison wrote:
Hello,
One client, running Access 2003, has noted that every time my
database starts, she gets a "this file may not be safe..." message.
My few other clients, running both 2002 and 2003 have had no such
problem. The program was developed in Access 2002.
Short of buying a digital signature for $431/year (ouch--I am a very
small operation), what can I do to help her. Access 2002 seems not
to have a macro security level like Excel (at least I can't find
it)--maybe it's in 2003. Even if so, I am reluctant to tell her to
set it on low.
Why? The macro security first appeared in Access in 2003, so you won't find
it in 2002. I would tell her to set the macro security to low. It's no more
dangerous than running the mdb in 2002. When was the last time you heard of
malicious code being run in a mdb?
--
Joan Wild
Microsoft Access MVP
.
- Follow-Ups:
- Re: Access 2003 security warnings
- From: Joan Wild
- Re: Access 2003 security warnings
- References:
- Access 2003 security warnings
- From: Richard Harison
- Re: Access 2003 security warnings
- From: Joan Wild
- Access 2003 security warnings
- Prev by Date: Re: Access 2003 security warnings
- Next by Date: Re: Access 2003 security warnings
- Previous by thread: Re: Access 2003 security warnings
- Next by thread: Re: Access 2003 security warnings
- Index(es):
Relevant Pages
|
