macro security error message

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

Guest

I have a customer who has access 2003, not the whole office suite installed.
Whenever he attempts to open a database he gets this blasted message about
how bad macros are and that he should not open it. It can be ignored, but it
is a real pain. This is normally cured by going to macro securtiy and
setting it low, but I find that macro security is grayed out and unavailable.
This is not the case on machines with the full version of office installed.
Anyone know a fix for this?
 
Welcome to Access 2003. Here is some info on this subject:
(Watch out for any possible line wrapping on these links)

**I believe this one applies to you the most**
You can to go Tools, Macro, Security and set it to low.
If the security item isn't on that menu, you may need to reset your menubar. See:
http://support.microsoft.com/default.aspx?scid=kb;en-us;833219&Product=acc2003

You can also manually add the following Registry keys:
Set registry as follows:

ROOT:Local Machine
Key: SOFTWARE\Microsoft\Jet\4.0\Engines
Name:SandBoxMode
Value:#00000002

ROOT:Local Machine
Key: Software\Microsoft\Office\11.0\Access\Security
Name:Level
Value:#00000001

If these are just for your use, you can create a self cert on your computer
and digitally sign your databases. More info at:
http://www.microsoft.com/resources/documentation/office/2003/all/reskit/en-us/seca02.mspx

Other link to see:
http://office.microsoft.com/assista...ID=CH010411421033&CTT=4&Origin=CH010411391033

Frequently asked questions about Access security warnings:
http://office.microsoft.com/assista...ID=HA011225981033&CTT=4&Origin=CH010411391033

More info here:
How to configure Jet 4.0 to prevent unsafe functions from running in Access 2003
http://support.microsoft.com/default.aspx?kbid=294698

Still more info here:
http://www.fmsinc.com/free/tips.html#accesstip19

Another link on the subject:
http://www.access.qbuilt.com/html/vba.html#SetMacroSecLvl

An online course:
http://office.microsoft.com/training/training.aspx?AssetID=RC011461801033

--
Jeff Conrad
Access Junkie
Bend, Oregon

in message:
 
And the easiest, simplest method - which Jeff steadfastly refuses to
add to his list, for some reason, despite the fact that this method has
already helped dozens of people:

* Write a 5-line script which uses the AutomationSecurity property
to disable the messages on a per-database basis. Google this newsgroup
for "automationsecurity" for details.

This method requires NO registry changes, NO setting macro security Low
for all programs, NO digital certificates, and NO reading complicated
articles about Office, Access or Jet security.

This method works fine unless your database is *secured* (which makes
it a harder but not impossible), or your PC is not allowed to run
scripts. But it only takes 5 minutes to check this method out, so it
should undoubtedly be your first port of call, when you want to solve
this problem.

HTH,
TC
 
Darn, I screwed up again TC!

I have this list saved in my Newsgroup Database.
At some point I created two lists (with different names) with
the same information. One of the lists does not have your
suggestion and one does. And yes, I copied/pasted the wrong
one again!!

I will delete the other one right now so I will not forget.

Sorry TC!
Bad Jeff.
 
Jeff

Further to this, I just realized that it was not you whom I had in
mind. It is another regular poster who always omits the option in
question. So, sorry for the abrupt tone of my complaint!

Cheers,
TC
 
TC said:
This method works fine unless your database is *secured* (which makes
it a harder but not impossible),
Click to expand...

Hi TC,

What modifications should be made to the code for a secured app?

Regards,
Keith.
 
It's not at all simple to get it working seamlessly with a secured
application. I discussed this here within the past few weeks. If you
google on automationsecurity you should easily find that thread :-)

Cheers,
TC
 
Back
Top