Re: unsafe functions message
- From: "Paul Overway" <paul@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 10 May 2005 20:33:10 -0400
The entries I indicated are EXACTLY what you need to type in if you're using
ADE to create a package. The # creates a dword vs sz.
--
Paul Overway
Logico Solutions
http://www.logico-solutions.com
"pookie bear" <pookiebear@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:14C07C97-ABB5-4433-93E3-A04DF3DC6524@xxxxxxxxxxxxxxxx
> Well I can see the certificate is out.
>
> I got to poking around and discovered the security dword that you mention.
> The stupid packager lets you dink with registry keys but it only puts out
> string entries for some reason sz as opposed to dword.
>
> The other thing I find strange is that you cannot package and put you
> files
> in a directory off the root, everything has to be sub of program files,
> only
> a problem cause its a lot easier to tell a client to be sure and backup
> directory xxx. Oh well thanks for taking the time to answer, now if I can
> just figure a way to get the installer to put the dword in i'll be set.
>
> "Paul Overway" wrote:
>
>> Code=macro.
>>
>> Thawte, Verisign for digital certificates. But good luck getting one
>> unless
>> you're listed with D&B. Also, you have to pay the $400 every 2 years.
>>
>> The simplest way around this is to change the macro security settings
>> during
>> install. You'll need to add/modify the following 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 your app is Sandbox safe, you can skip the first one...but 2 is the
>> default setting anyway....you shouldn't set it to 0 (as indicated in your
>> original post). Sandbox at 2 works fine for Access apps.
>>
>> --
>> Paul Overway
>> Logico Solutions
>> http://www.logico-solutions.com
>>
>>
>> "pookie bear" <pookiebear@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:876252C0-FD27-4E88-B7BB-485A45655102@xxxxxxxxxxxxxxxx
>> > Thanks Paul,
>> > I figured it was macro security finny the db does not use macros. In
>> > any
>> > event since my clientel may not be using office how can I change the
>> > macro
>> > security level in runtime?
>> >
>> > Who sells digital certificates?
>> >
>> > Kim
>> >
>> > "Paul Overway" wrote:
>> >
>> >> You either need to:
>> >>
>> >> a) buy a digital certificate and sign your database
>> >> b) set macro security to low on any PC where your database will be
>> >> installed
>> >> c) use a VB script to open your database after setting macro security
>> >> to
>> >> low
>> >> through automation (impossible with runtime)
>> >>
>> >> The sandbox setting only applies to "unsafe expressions" in queries.
>> >> Macro
>> >> security is what is tripping you up.
>> >>
>> >> --
>> >> Paul Overway
>> >> Logico Solutions
>> >> http://www.logico-solutions.com
>> >>
>> >>
>> >> "pookie bear" <pookiebear@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:06A8FA09-BC39-4EEF-A655-C612E5B0151B@xxxxxxxxxxxxxxxx
>> >> > Boy am I frustrated,
>> >> >
>> >> > I am trying to package a database (2003) for deployment using
>> >> > runtime.
>> >> > I
>> >> > use
>> >> > a lot of code but no macros. It goes through the wizards just fine
>> >> > including
>> >> > the sandbox check. But when I install it on the target machine
>> >> > (using
>> >> > the
>> >> > runtime). I get the "unsafe functions error". Obviously I can't have
>> >> > my
>> >> > clients having to thread though all these messages each time they
>> >> > open
>> >> > the
>> >> > database. According to the KB article 294698 setting the sandbox reg
>> >> > entry
>> >> > to
>> >> > 0 ought to stop this, but it doesn't.
>> >> >
>> >> > Any help would be apreciated kim@xxxxxxxxx
>> >>
>> >>
>> >>
>>
>>
>>
.
- Follow-Ups:
- Re: unsafe functions message
- From: pookie bear
- Re: unsafe functions message
- References:
- unsafe functions message
- From: pookie bear
- Re: unsafe functions message
- From: Paul Overway
- Re: unsafe functions message
- From: pookie bear
- Re: unsafe functions message
- From: Paul Overway
- Re: unsafe functions message
- From: pookie bear
- unsafe functions message
- Prev by Date: Re: unsafe functions message
- Next by Date: Re: Access 2003 Developer Extensions error
- Previous by thread: Re: unsafe functions message
- Next by thread: Re: unsafe functions message
- Index(es):
Relevant Pages
|