Hi,

Under the tools menu, think under the macros menu set the security to low,
the other reason can be that you need to update the Jet SP to version 8,
this can be downloaded from

http://www.microsoft.com/data you are looking for SP8 for Jet.

Hope it helps.

Welcome to Access 2003! Here is some info on this subject:
(Watch out for any possible line wrapping on these links)

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/se
ca02.mspx

Other link to see:
http://office.microsoft.com/assistance/category.aspx?TopLevelCat=CH790018001033&
CategoryID=CH010411421033&CTT=4&Origin=CH010411391033

Frequently asked questions about Access security warnings:
http://office.microsoft.com/assistance/preview.aspx?AssetID=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

And a very interesting work-around presented by TC:

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.usercontrol=true
  set o=nothing