Macro Security Information for Access 2003
Here is some information on the new macro security feature introduced in Access
2003.
1. 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
2. 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
3. Other link to see:
http://office.microsoft.com/assistance/category.aspx?TopLevelCat=
CH790018001033&CategoryID=CH010411421033&CTT=4&Origin=CH010411391033
4. Frequently asked questions about Access security warnings:
http://office.microsoft.com/assistance/preview.aspx?AssetID=
HA011225981033&CTT=4&Origin=CH010411391033
5. 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
6. Still more info here (Tip 19
in the list):
http://www.fmsinc.com/free/tips.html#accesstip19
 7. Another link on the subject:
http://www.access.qbuilt.com/html/vba5.html#SetMacroSecLvl
8. An online course
http://office.microsoft.com/training/training.aspx?AssetID=RC011461801033
9. And a very interesting work-around presented by
newsgroup regular TC
This particular technique, however, will not work with a secured database:
"IMO the best way is to start the database via a script file which sets
the macro security level to low for that single invocation of Access.
This does not require a certificate, or a registry change, and it does
not affect any other database(s) - just the one being started by that
script."
Eg. in VBScript:
dim o
set o=createobject ("Access.Application")
o.automationsecurity=1 ' set macro security LOW.
o.opencurrentdatabase "full path to your database"
o.visible=true
o.usercontrol=true
set o=nothing
Starting the application from the
script will usually result in the application window being smaller.
To have the application maximized, follow these additional instructions by
TC:
Try one of these two ways:
(1) Put the following statement somewhere in the startup code of your
database:
Application.RunCommand acCmdAppMaximize
Or:
(2) Assuming that your script says this:
dim o
set o = createobject ("access.application")
(etc.)
Add the following line before the (etc.):
o.runcommand 10
Method (1) is probably easier, and has the advantage that it will still
happen if the user chooses to ignore the script & open the database
directly.
10.
Here is a little utility to call up the Macro Security dialog box:
http://www.utteraccess.com/forums/showflat.php?Cat=&Board=81&Number
=1098473&page=0&view=collapsed&sb=5&o=&fpart=1
 Top
|
