Re: Getting Rid of Warnings

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Albert D. Kallal (PleaseNOOOsPAMMkallal_at_msn.com)
Date: 07/30/04 

Date: Fri, 30 Jul 2004 05:38:47 -0600

"Chris Mills" <phad_nospam@cleardotnet.nz> wrote in message
news:uJvKKqddEHA.3212@TK2MSFTNGP12.phx.gbl...
> He was complaining about users and a PDW-distributed package (not his own
> machine), so though good advice it barely seems appropriate. Maybe it can
be
> stuck into PDW.

The packaging installer allows you to add registry keys during the install.
I posted and answers to MANY people who asked on this subject.

You simply add the following two keys to the package install, and all nags
messages will disappear:

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

The first setting sets JET to sandbox mode for non ms-access applications.
The 2nd setting sets the macro security to low. It is also possible to
incorporate the security setting menu into the runtime if you want to make
the security setting a user option (I tested this, and simply building a
menu bar and stealing (copy) the security menu into a custom menu bar works
fine in the runtime.).

So, it is VERY easy to get rid of the security prompts, or VERY easy to
supply the end users with a menu option in the application. 

-- 
Albert D. Kallal   (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.attcanada.net/~kallal.msn

Relevant Pages

  • Re: Getting Rid of Warnings
    ... > The packaging installer allows you to add registry keys during the ... > You simply add the following two keys to the package install, ... > The first setting sets JET to sandbox mode for non ms-access applications. ... > The 2nd setting sets the macro security to low. ...
    (microsoft.public.access.devtoolkits)
  • Re: CLiki and ALU Wiki sites massively spammed
    ... > Getting the author keys is too hard, ... It's not that you've totally thrown out security, ... so it's possible that some lisp package maintainer you trust could do ... default wwwkeys server I was using. ...
    (comp.lang.lisp)
  • TSLSA-2006-0024 - multi
    ... Trustix Secure Linux Security Advisory #2006-0024 ... Affected versions: Trustix Secure Linux 2.2 ... Package description: ... Mu Security has reported a vulnerability in Cyrus SASL ...
    (Bugtraq)
  • Re: OT - Kuwait
    ... > strict security procedures to prevent unauthorized release of the keys. ... > established their authority to acquire the content of those communications ... Every one but you knows the government has been evesdropping on email & ... Social Security Administration have computer files on nearly all Americans. ...
    (alt.sports.football.pro.ne-patriots)
  • [Full-disclosure] SUSE Security Announcement: openwsman (SUSE-SA:2008:041)
    ... Security Vulnerability Resolved: ... Package Location and Checksums ... SUSE security announcements are published via mailing lists and on Web ... guaranteed by a cryptographic signature in each announcement. ...
    (Full-Disclosure)