Conrad Systems Development

Conrad Systems Development



  Client List

Access Information
  App Close Button
  Macro Security
  Kick Them Off
  Database Splitting
  Combo Boxes
  Tab Colors
  Progress Bars
  Command Buttons
  Demo Database
  Form Resize
  TreeView Control
  Switchboard FAQ
  Matching Games
  Top 10 Lists
  CSD Tools
  Technical Articles
  Document Tables
  Shift Key Bypass
  Epson Printer Info
  Newsgroup Help

  Contact Us

                                 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:;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

ROOT:Local Machine
Key: Software\Microsoft\Office\11.0\Access\Security

3. Other link to see:

4. Frequently asked questions about Access security warnings:

5. More info here:
How to configure Jet 4.0 to prevent unsafe functions from running in Access 2003

6. Still more info here (Tip 19 in the list):

7. Another link on the subject:

8. An online course

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

Eg. in VBScript:

dim o
set o=createobject ("Access.Application")
o.automationsecurity=1  ' set macro security LOW.
o.opencurrentdatabase "full path to your database"
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

Application.RunCommand acCmdAppMaximize


(2) Assuming that your script says this:

dim o
set o = createobject ("access.application")

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

10. Here is a little utility to call up the Macro Security dialog box:


Top Top

Copyright 2005-2010 Conrad Systems Development - All Rights Reserved

This page was last updated on Sunday, September 19, 2010.

Site created with FrontPage