Access 2003 Run-Time

[Fog Line]

Can anyone tell me how to turn off the warningevery time you start my App?
I use Access 2003 and deploy my App with access 2003 run time.
and even in run time I still get the warning.
How do you disable it??
Thanks
Ray

 

[Fog Line]

I know how to disable it in the Tools menu.
But how do you disable it when using run-time??

 

[Scott McDaniel]

I know how to disable it in the Tools menu.
But how do you disable it when using run-time??

By "Tools" menu, do you mean setting the Macro security to Low? This can be done, but it's not the path recommended by
MS. That said, I believe there are a few registry keys you can set to avoid this:

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

See this for info on turning off these warnings:
http://office.microsoft.com/en-us/access/HA011225981033.aspx#180

See the ng posting, with a copy/paste from Jeff Conrad about the various ways to get around the warnings:
http://groups.google.com/group/micr...ecurity+registry+keys&rnum=1#c455e96f65433fdb


Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

 

[Fog Line]

Thanks Scott
I use Installsheld to deploy my App with Access 2003 Run Time
I'll will add the:
////////////////////////////////////////////////////////////////////////////
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
//////////////////////////////////////////////////////////////////////////
to my istall setup and try that.
Thanks for you time.
Ray White

 

[Scott McDaniel]

Personally, I'd go the digital certificate route (I have gone that route) and NOT muck with an enduser's security
configuration. Granted the chances of infection are so remote as to be nonexistant, but many of my corporate clients
would be extremely put out if they found that my app reset their security config, and as a result a virus infected their
networks. My apps are in use at several NASA facilities, along with some very secure aerospace companies and their IT
depts simply do not tolerate messing with security settings.

Another innovative idea was put forth by TC on the newsgroups - use a VBScript file to launch your application, and set
the Macro security to Low for ONLY that session of Access ... basically you'd store the current setting, then reset to
Low, launch the app, then have the Access app reset the reg keys when it exits ... this allows you to keep the user's
settings intact while manipulating them for your application only. See the link I posted earlier (the one to the ng
posting) for more info on that.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com