Hi.
It's because you have your Access Macro Security level set to Medium. When
it's set to Medium, you're asking Access to check whether or not the
database file you want to open contains any VBA code, action queries, or
unsafe expressions in either queries or properties on forms or reports. The
database you developed surely does, so Access is reporting this information
to you correctly and asking you if you really, really want to open this
potentially dangerous file. Since you developed the database file yourself,
you can make an informed decision.
However, I started this database on MY
computer. I would understand if someone had sent it to me, but I created
it.
Access Macro Security is not capable of determining ownership or the
origination of the database, or whether or not the file contains a virus, or
whether or not the it contains malicious content. It can only check whether
or not the database file contains VBA code, action queries, or unsafe
expressions in certain places, which are queries and the properties of forms
and reports. Since your database contains VBA code, action queries, or
unsafe expressions, you receive the warnings.
What can I do to stop getting this everytime I open the database? I have
my
security settings on Medium (I think) and I don't really want to change
that.
Yes. It's set on Medium. If it were set on High, then you wouldn't be
allowed to choose whether or not to open the file. You would just be warned
that you cannot open the file. If it were set on Low, then you wouldn't
receive these warnings.
Since you're dead set on keeping your Access Macro Security level on Medium,
you have three choices to avoid the warnings. You can:
1.) Sign the database file with a digital certificate and resign it every
time you make changes, because changes will invalidate the digital
certificate; or
2.) Remove all of the VBA code, action queries, and unsafe expressions from
the database file; or
3.) Use an earlier version of Access which doesn't have Access Macro
Security to develop your Access databases in.
If you find these alternatives impractical, then you will have to live with
the prompts acknowledging that your databases have VBA code, action queries,
and/or unsafe expressions and requesting that you give your permission to
open them every time.
And since you're new to Access, I'll tell you what most experienced Access
developers do in Access 2003. We keep our antivirus definitions up to date,
scan all incoming files (downloaded from the Internet, or E-mailed to us, or
retrieved from across the network, because that's the only way to detect
whether or not the file has a virus, and that's really what we want this
type of computer security for when opening our database files), scan our
hard drives for viruses on a regular basis, and keep the Access Macro
Security level set to Low.
Setting the Access Macro Security to Medium or High doesn't keep our
computers as secure as it sounds like it will. Macro Security for other
Office applications makes some sense security-wise, because they work
without VBA, action queries, or unsafe expressions, but if an Access
database is at all useful, it certainly has VBA, action queries, and unsafe
expressions.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs:
www.DataDevilDog.BlogSpot.com,
www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
