Security warning when opening a file

[Guest]

I'm getting a security warning when opening a file.
Tried to set Tools->Macros->security from Medium to Low, but it keeps on
geting back to Medium.
Any ideas?
Thanks.

 

[Billy]

You do not setup security on the Micros. It could be that your file is
not refering to the right MDW file. If you write down what that
security warning says, I may be able to figure out what the problem is.

 

[Guest]

Hi, Billy
I'm tring to open an Access file that has macros.
The message on opening the file is: "Secutiry Warning: This file may not be
safe if it contains code that was intended to harm your computer. Do you want
to open this file or cancel the operation?" Cancel, Open and More Info
buttons in the messagebox.
As i said, I'm not able to resolve the issues.
Thanks,
Yoav

 

[Rick Brandt]

Hi, Billy
I'm tring to open an Access file that has macros.
The message on opening the file is: "Secutiry Warning: This file may
not be safe if it contains code that was intended to harm your
computer. Do you want to open this file or cancel the operation?"
Cancel, Open and More Info buttons in the messagebox.
As i said, I'm not able to resolve the issues.
Thanks,
Yoav

Are you running on a corporate network? If you are setting this to "Low" and
it is changing back to "Medium" then it might be because of a security
policy being invoked by your login script.

 

[Guest]

Rick, thanks for your reply.

You're right, I am using a corporate computer. this security notice prevents
me of using a batch file (that runs a macro) which is schedule to run at
night.
What can I do?
Again, Thanks.

 

[Rick Brandt]

Rick, thanks for your reply.

You're right, I am using a corporate computer. this security notice
prevents me of using a batch file (that runs a macro) which is
schedule to run at night.
What can I do?
Again, Thanks.

You might have to have the app digitally signed to avoid the issue. I can't
say with more confidence because I have avoided Access 2003 for this very
reason.

 

[Guest]

The digital signature did the trick.
Thanks!

You might have to have the app digitally signed to avoid the issue. I can't
say with more confidence because I have avoided Access 2003 for this very
reason.