What to do next??

  • Thread starter Thread starter Jim May
  • Start date Start date
J

Jim May

Running WinXP-Home -All updates installed.
Just loaded Office 2003 Pro Edition Full Install
Have only one active *.mdb file (created in Acc97)
that I wish to view. When I double-click on it the
message comes up:

"SECURITY WARNING"
This file may not be safe...
Do you want to open this file or cancel the operation?

What steps need I follow to eliminate this warning?
Thanks in advance..
 
go ahead and open the file. then, on the menu bar, click Tools | Macro |
Security, and on the Security Level tab, select the Low setting and click
OK. as long as you don't open Access databases from unknown/untrusted
sources, you'll be fine.

hth
 
Two Q's: (I am Access single-user - Win XP)
1) On my present one mdb file can I create a Macro
On start up that will set the Macro Security level to Low (while I am in the
file), then "reset" Security level back to Medium when Closing (exiting -
Access)?
2) Unfortunately, I went to Tools, Security >> User-level Security Wizard
and stepped through modifying (i think) my workgroup file <<< which I
really didn't need to do;
How can I "remove this now recurring step" that come up each time I load my
file?
Tks in advance..
 
comments inline.

Jim May said:
Two Q's: (I am Access single-user - Win XP)
1) On my present one mdb file can I create a Macro
On start up that will set the Macro Security level to Low (while I am in the
file), then "reset" Security level back to Medium when Closing (exiting -
Access)?

offhand, i'd guess no. the macro security level is a software-specific
setting, not file-specific. AFAIK, the system is checking the file *before*
it opens, not after. you could always try it, but i couldn't tell you how.
2) Unfortunately, I went to Tools, Security >> User-level Security Wizard
and stepped through modifying (i think) my workgroup file <<< which I
really didn't need to do;
How can I "remove this now recurring step" that come up each time I load my
file?

well, if you modified the built-in Access user security, i can't help you,
as i have no experience with it at all. suggest you start a new thread for
that particular issue, in the microsoft.pulic.access.security newsgroup.
some of the best "security folks" keep an eye on that newsgroup (like Joan
Wild, for instance).

for further help re the *macro* security issue you originally asked about,
see Jeff Conrad's post in this thread for a link to tons of info.

hth
 
Back
Top