Group:  Microsoft Access ยป microsoft.public.access.gettingstarted
Thread: Access Runtime Startup Messages

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

Access Runtime Startup Messages
"Terry Willerton" <terrywillerton[ at ]yahoo[trousers].co.uk> 08.08.2006 15:20:20
Hi

i have just made my first database using the runtime option, and wish to
distribute this to all our office pc's none of which have access.

The problem i have got is that when starting the application the user gets
three messages warning bout security and such like. is there a way to turn
these options off in the runtime version like their is in the full version
??

please email a response

remove trousers for correct e-mail address



Re: Access Runtime Startup Messages
"Albert D. Kallal" <PleaseNOOOsPAMmkallal[ at ]msn.com> 09.08.2006 08:10:23
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
pleaseNOOSpamKallal[ at ]msn.com


Re: Access Runtime Startup Messages
paddyIE 26.09.2006 16:13:01
Albert,

Sorry to be hardheaded here, but, having the same problem I looked into your
solution. Yes I can add the registration values in the package wizard but I
have a question. 1.) in your example you included the "#" sign and
"00000002". Just for grins I used regedit to look at my registry. For the
Sandbox value it was 0x00000002. Then if you dblclick to edit, the input just
shows a single digit.

Also I don't have the ....\Access\Security on my working machine. Would this
be a new entry and would it also need the "#" as you showed?

Knowing the danger of the registry, I am Over Cautious with these activities
and as a result want to double check before actually making changes.

Sorry to be a pain.
--
Patrick
Still trying to figure out what the meaning of IS is.


"Albert D. Kallal" wrote:

[Quoted Text]
> 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
> pleaseNOOSpamKallal[ at ]msn.com
>
>
>
Re: Access Runtime Startup Messages
paddyIE 28.09.2006 19:18:01
Albert,

Did it anyway. Worked great. Thanks. Disregard previous post.
--
Patrick


"paddyIE" wrote:

[Quoted Text]
> Albert,
>
> Sorry to be hardheaded here, but, having the same problem I looked into your
> solution. Yes I can add the registration values in the package wizard but I
> have a question. 1.) in your example you included the "#" sign and
> "00000002". Just for grins I used regedit to look at my registry. For the
> Sandbox value it was 0x00000002. Then if you dblclick to edit, the input just
> shows a single digit.
>
> Also I don't have the ....\Access\Security on my working machine. Would this
> be a new entry and would it also need the "#" as you showed?
>
> Knowing the danger of the registry, I am Over Cautious with these activities
> and as a result want to double check before actually making changes.
>
> Sorry to be a pain.
> --
> Patrick
> Still trying to figure out what the meaning of IS is.
>
>
> "Albert D. Kallal" wrote:
>
> > 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
> > pleaseNOOSpamKallal[ at ]msn.com
> >
> >
> >
Re: Access Runtime Startup Messages
Angus 30.09.2006 16:30:01
Paddy,

What EXACTLY did you do? As you said, the instructions are not quite
clear. Does this solve the problems for all users of a PC? Is there
similarly a way to configure the options under Tools/Options in this way?

Thanks in advance.

"paddyIE" wrote:

[Quoted Text]
> Albert,
>
> Did it anyway. Worked great. Thanks. Disregard previous post.
> --
> Patrick
>
>
> "paddyIE" wrote:
>
> > Albert,
> >
> > Sorry to be hardheaded here, but, having the same problem I looked into your
> > solution. Yes I can add the registration values in the package wizard but I
> > have a question. 1.) in your example you included the "#" sign and
> > "00000002". Just for grins I used regedit to look at my registry. For the
> > Sandbox value it was 0x00000002. Then if you dblclick to edit, the input just
> > shows a single digit.
> >
> > Also I don't have the ....\Access\Security on my working machine. Would this
> > be a new entry and would it also need the "#" as you showed?
> >
> > Knowing the danger of the registry, I am Over Cautious with these activities
> > and as a result want to double check before actually making changes.
> >
> > Sorry to be a pain.
> > --
> > Patrick
> > Still trying to figure out what the meaning of IS is.
> >
> >
> > "Albert D. Kallal" wrote:
> >
> > > 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
> > > pleaseNOOSpamKallal[ at ]msn.com
> > >
> > >
> > >

Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net