Macro Security selection wont hold

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have recently switched to Office 2003 and Access 2003. I have followed the
instructions in the help file to set the Macro security level in my databases
from Medium to Low. For some reason when I select the Low setting and click
ok the selection does not hold true. I know we have security already in
place so all of the macros and people accessing my databases are safe. how
do I get the security level to hold so I can eliminate the security warning
window that displays everytime I open my databases either with scheduled
tasks to run macro for automation or manually?

Thank you for your assitance with this.
 
Ryan Huth said:
I have recently switched to Office 2003 and Access 2003. I have followed
the
instructions in the help file to set the Macro security level in my
databases
from Medium to Low. For some reason when I select the Low setting and
click
ok the selection does not hold true. I know we have security already in
place so all of the macros and people accessing my databases are safe.
how
do I get the security level to hold so I can eliminate the security
warning
window that displays everytime I open my databases either with scheduled
tasks to run macro for automation or manually?

Thank you for your assitance with this.
Click to expand...

I have this problem at my place of work and it's a corporate restriction
which has been decided upon by our IT "experts". I can't even save this
setting on a "per application" basis.

Regards,
Keith.
www.keithwilby.com
 
If only it /could be/ defined "per application"!

Why not use my "automationsecurity" trick? (google is your friend etc.)

TC
 
TC said:
If only it /could be/ defined "per application"!

Why not use my "automationsecurity" trick? (google is your friend etc.)
Click to expand...
I did look into that but since my apps are secured I decided that it was
more work than I could afford to do just now.
 
Understood. I got a general solution /nearly/ working for secured db's,
but it wasn't quite right, & I didn't have the time to fix it. That's
fine when the user is me, & I know how it works, & I can change it as
required - but not so fine when someone else tries it, & it doesn't
work 100%, & they don't know how to fix it.

It's on my list to get back to, if & when I have time :-)

Cheers,
TC
(off for the day)
 
Back
Top