"This file may not be safe" messaage after converting db from access '97 to 2003.

"This file may not be safe" messaage after converting db from access '97 to 2003.

Post by Pat McCan » Sat, 04 Sep 2004 05:26:05


Hi all
Have just put a database written under access 97 on a machine with
2003. I got an initial warning message about "unsafe expressions not
being blocked" which sugessted I needed to load Jet 4 servicepack 8,
which I did. That sorted that but I now get a "this file may not be
safe" message and have to click yes to the prompt everytime I open the
database to use it.

I want to stop the warning coming up, and to do that it seems I need
a digitally signed certificate. Is this true? if so, how do I create
one and apply it to my database? (I wrote the database)

Thanks Pat
 
 
 

"This file may not be safe" messaage after converting db from access '97 to 2003.

Post by Rajes » Sat, 04 Sep 2004 06:25:16

If u are concerned about the security , go to macros-->
then security and then-- security level tab--> change the
option to lower security. and then this window doesnt pop
up any more.

The otherway is to create a digital signature.. search
microsoft site for this...

Hope this helps.

Mike

machine with
expressions not
servicepack 8,
may not be
everytime I open the
seems I need
do I create

 
 
 

"This file may not be safe" messaage after converting db from access '97 to 2003.

Post by raghup » Sat, 04 Sep 2004 15:13:26

i Pat,

This is becuase of your security settings, you can easily change the level
of securty to not inform you.

When you open a file in Access 2003, you might see a warning that states
that the file may be unsafe if it contains code that was intended to harm
your computer.

You may see the following warning when opening a file, if the macro
security level in Access is set to High:

Access cannot open the file due to security restrictions. Security settings
restrict access to the file because it is not digitally signed.

You may also see other similar warnings about your file not being safe.

These messages are a result of new security features that are part of
Access 2003. For more information about these security features and how to
avoid these warnings from appearing each time you open a file, see
Frequently asked questions about Access security warnings.


http://office.microsoft.com/en-us/assistance/HA011071651033.aspx


Macro security levels

The following information summarizes how macro (macro: An action or a set
of actions you can use to automate tasks. Macros are recorded in the Visual
Basic for Applications programming language.) virus protection works under
each setting on the Security Level tab in the Security dialog box (Tools
menu, Macro submenu) under different conditions. Under all settings, if
antivirus software that works with Microsoft Office 2003 is installed and
the file contains macros, the file is scanned for known viruses (virus: A
computer program or macro that "infects" computer files by inserting copies
of itself into those files. When the infected file is loaded into memory,
the virus can infect other files. Viruses often have harmful side effects.)
before it is opened.

Security Because macros can contain viruses, be careful about running
them. Take the following precautions: run up-to-date antivirus software on
your computer; set your macro security level to high; clear the Trust all
installed add-ins and templates check box; use digital signatures; maintain
a list of trusted publishers.

Very High

This setting is not available in the Security dialog box in Microsoft
Office Access 2003. It is possible, however, to use system policies to set
the security level in Access to Very High. When the security level is set
to Very High, Access cannot open any Access database (Microsoft Access
database: A collection of data and objects (such as tables, queries, or
forms) that is related to a particular topic or purpose. The Microsoft Jet
database engine manages the data.) or Access project (Microsoft Access
project: An Access file that connects to a Microsoft SQL Server database
and is used to create client/server applications. A project file doesn't
contain any data or data-definition-based objects such as tables and
views.) files.

High

Unsigned macros
The file can be opened only if the user chooses to trust the author and
certification authority.

Signed macros

The source of the macro and the status of the signature (digital signature:
An electronic, encryption-based, secure stamp of authentication on a macro
or document. This signature confirms that the macro or document originated
from the signer and has not been altered.) determine how signed macros are
handled.

A trusted source. Signature is valid.

Macros are automatically enabled, and the file is opened.

An unknown author. Signature i