how can i remove the startup warning of access

[jetro=)]

everytime i open my database there is always a security warning, warning me
that the macros may be harmful, but it is my own macro how can i remove it ???

 

[George]

Assuming that you have Office 2003, try:
Tools - Macros - Security and select Low

George

Ο χÏήστης "jetro=)" έγγÏαψε:

 

[Rick Brandt]

Assuming that you have Office 2003, try:
Tools - Macros - Security and select Low

I think that advising users to lower their security settings is
irresponsible. [snip]

Why? All it does is make Access 2003 work the same way every other version of
Access has ever worked.

 

[zealoty]

You really dont want to screw with security settings....... check this
page out.
http://pubs.logicalexpressions.com/Pub0009/LPMArticle.asp?ID=194

 

[Rick Brandt]

Jamie Collins wrote:
[snip]

Maybe Access 2003 was made more secure for a reason?

Jamie.

Marketing and the lawyers made this decision. Have you EVER seen a user
encounter those warnings without saying "yes" to all of them? Given that
the user will virtually always bypass the messages then what purpose do they
serve? They are an annoyance only.

If the messages were only displayed when opening files located on a
non-trusted site then they would make sense. To have them appear for every
file opened is just stupid.

 

[jetro=)]

is that warning something to do with our linux server?

 

[George]

I was just trying to help somebody in here. I got a lot of answers from this
group and I appreciate a lot the professionals' answers.

From my experience (although I don't consider myself a professional Access
Developer) I have never seen any user to use this warning message to block
macros etc, they and my self always ignore it.

But, finally if there is any reason of not setting the Security level to Low
can anybody tell me?

Thanks

Ο χÏήστης "Rick Brandt" έγγÏαψε:

Jamie Collins wrote:
[snip]

Maybe Access 2003 was made more secure for a reason?

Jamie.

Marketing and the lawyers made this decision. Have you EVER seen a user
encounter those warnings without saying "yes" to all of them? Given that
the user will virtually always bypass the messages then what purpose do they
serve? They are an annoyance only.

If the messages were only displayed when opening files located on a
non-trusted site then they would make sense. To have them appear for every
file opened is just stupid.

 

['69 Camaro]

Hi.

is that warning something to do with our linux server?

No. The default setting for Access Macro Security is medium, so unless you
change this setting or authenticate your own files with a digital signature,
you'll get the warning when you attempt to open the file.

But please tell me you're _not_ storing the Access database file on a Linux
server.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

['69 Camaro]

Hi, Jamie.

ALTER DATABASE PASSWORD NULL administrator;
GRANT ALL PRIVILEGES ON [all my objects] TO [all my users];

Are you trying to say that George is advocating opening the door for
everyone into the database? If so, may I remind you that, by default,
there's no database password set on Access databases, a state that most
Access databases remain in? And even when they don't, there are free tools
available (or for a small price if one doesn't know where to look) that will
reveal the database password, so trying to secure the database with a
database password will keep only the most basic computer novices out of the
database.

May I also remind you that, by default, User-level Security is set so that
the Admin user is the owner of the database and all objects, and everyone
who opens the database _is_ the Admin user? So everyone who opens the
database has all priviledges on all objects, anyway. This is a state that
most Access databases remain in, even when User-level security is attempted,
because most people do it incorrectly the first few times.

In other words, the Access security door is almost always open, or can
easily be opened, so criticizing George for his "open door policy" serves no
purpose.

Maybe Access 2003 was made more secure for a reason?

If you think Access 2003 is more secure than earlier versions, then you are
mistaken. The Macro Security doesn't detect viruses, so it doesn't keep
one's computer "safe." The Macro Security warning gets ignored every time
an Access user opens a database when the setting is set to Medium. And when
it's set to High, the user can't open it unless it's digitally signed with a
certificate issued by a formal Certificate Authority, an expense most
organizations avoid. So if the Access user needs the database to do his
job, he either opens it with an earlier version of Access or he ends up
changing the Macro Security setting to a lower one in order to open the
database -- and ignores the warnings.

And what the Macro Security checks is whether there's VBA code and whether
there's certain expressions used in queries or in object properties, not
whether or not the file contains malicious code or expressions. It's like
throwing the baby out with the bath water, and since the Macro Security
can't discern between good and bad and doesn't even detect viruses, its
warnings get ignored.

Which is why Access 2003 is more annoying, but no more secure than earlier
versions of Access which lack this Macro Security "feature." And it's why
Microsoft changed this feature in Access 2007 so that there's a safe zone
that the Access user can set where all Access databases located there will
be trusted, thereby giving the user control over which files are safe (his
own) and which files should be eyed with suspicion (others', especially
those from outside of the organization) -- and allowing the Access user to
consider the Macro Security warning as it was intended -- if he hasn't
already been desensitized by the little boy crying wolf so often in Access
2003.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

Why? All it does is make Access 2003 work the same way every other
version of
Access has ever worked.

ALTER DATABASE PASSWORD NULL administrator;
GRANT ALL PRIVILEGES ON [all my objects] TO [all my users];

Use MEMO for all your table columns (Why? All it does is make Access
2003 work the same way every version of Excel has ever worked.)

If you want to prop open a fire door, there's usually a fire
extinguisher near by.

Sensible answer: caution required when disabling safety features.

George gave no caution. A simple workaround is available without
modifying security settings. Isn't that better advice, Rick?

Maybe Access 2003 was made more secure for a reason?

Jamie.

 

['69 Camaro]

Hi, George.

I was just trying to help somebody in here.

Please continue to do so. Plenty of people need plenty of help with Access.
Jamie Collins enjoys making himself feel superior to others, so take what he
says with a grain of salt. Many of the regular posters have placed him in
their kill files. While you can't do that with your Web newsreader, you can
just skip reading his posts whenever you see his name. FYI, he also goes by
other names, such as onedaywhen and peregenem.

But, finally if there is any reason of not setting the Security level to
Low
can anybody tell me?

It's difficult to think of such a scenario, but perhaps Jamie can answer
this question better than I can, since he believes the setting should never
be low. He must have been been bitten by a malicious Access database when
he had it on low if he's an advocate of Access's Macro Security, although
I've never heard of any reports of such an Access database.

Leave the Macro Security setting on low when working with your own files,
but when you go on the Internet to download someone else's database example,
put your Macro Security setting on medium before attempting to open the
file. Of course, you'd scan the file first with your anti-virus software to
determine whether there is a virus embedded in the file. Then attempt to
open the file. If the Macro Security warning tells you it may be harmful,
don't open it -- yet. This just tells you that the file either contains an
expression that Jet can block (such as "Quit" to close applications, or an
action query that might delete or change the data) or contains any VBA code.
And any Access database file worth anything has at least some VBA code in
it, so you'll almost always get the warning. Enable the AllowBypass key on
the file and then hold the <SHIFT> key down while opening the database so
that the startup code doesn't run, then investigate whether there actually
is any harmful VBA code or expressions. In almost all cases, the
expressions or code that may be deemed harmful by Jet are legitimate and
intentionally placed there by the Access developer to aid in the
functionality of the database application.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

I was just trying to help somebody in here. I got a lot of answers from
this
group and I appreciate a lot the professionals' answers.

From my experience (although I don't consider myself a professional Access
Developer) I have never seen any user to use this warning message to block
macros etc, they and my self always ignore it.

But, finally if there is any reason of not setting the Security level to
Low
can anybody tell me?

Thanks

? ??????? "Rick Brandt" ???????:

Jamie Collins wrote:
[snip]

Maybe Access 2003 was made more secure for a reason?

Jamie.

Marketing and the lawyers made this decision. Have you EVER seen a user
encounter those warnings without saying "yes" to all of them? Given that
the user will virtually always bypass the messages then what purpose do
they
serve? They are an annoyance only.

If the messages were only displayed when opening files located on a
non-trusted site then they would make sense. To have them appear for
every
file opened is just stupid.

 

[Larry Linson]

Sorry, Jamie, Gunny's advice was correct:

(1) You can safely set security to Low (actually, if it were possible, you
could safely set it to Nonexistent) when executing your own databases or
trusted ones (e.g., something prepared and long and widely used in your own
organization).

(2) Take security precautions when executing databases you downloaded from
the Internet or got from an untrusted source.

The only reason I can think of for _not_ running your own databases on Low
security is that you might forget to set it to Medium or greater when you
obtained a new one from someone else.

On the other hand, there's nothing wrong with self-signing your own
databases, either, except it's a bit of extra work.

Larry Linson
Microsoft Access MVP