In Access 2003 I turn off all the warning messages in the Edit/Find tab under
Tools + Options for my data base. I then package it with the Access 2003
Developer Extensions Tools Wizard into a .dme runtime package. When I run
it on another computer other than mine, a computer with Access on it or one
without Access on it, I get all the warning messages for macros and queries,
as if I never turned off the Warning messages in the Edit/Find tab. Any
ideas??

"Bitsy" <(E-Mail Removed)> wrote in message
news:348B8C5C-987F-4A44-85E0-(E-Mail Removed)...
> In Access 2003 I turn off all the warning messages in the Edit/Find tab under
> Tools + Options for my data base. I then package it with the Access 2003
> Developer Extensions Tools Wizard into a .dme runtime package. When I run
> it on another computer other than mine, a computer with Access on it or one
> without Access on it, I get all the warning messages for macros and queries,
> as if I never turned off the Warning messages in the Edit/Find tab. Any
> ideas??

Yeah, those options are for "your installation of Access" Only a few of the
options in Tools - Options are "for this particular file" and they are labeled
as such.

If you're far enough along in Access development to be packaging solutions with
the Developer's Extensions you should not be using macros (especially in the
Runtime). Action queries can avoid the prompts by using either...

DoCmd.SetWarnings False
DoCmd.OpenQuery (or DoCmd.RunSQL)
DoCmd.SetWarnings True

or (even better)

CurrentDB.Execute "QueryName", dbFailOnError

The latter does not produce the prompts in the first place.



--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Simply add the following keys to your runtime packing (the package wizard
does have provision for adding regs keys).

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 you add both tof the above, then you get no security prompts at
all...even if the later jet sp8 is NOT installed. It is clean...and no
prompts....


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(E-Mail Removed)
http://www.members.shaw.ca/AlbertKallal