Access Runtime Startup Messages

[Terry Willerton]

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

 

[Albert D. Kallal]

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....

 

[Guest]

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.

 

[Guest]

Albert,

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

 

[Guest]

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.

 

[Guest]

Angus,

I did exactly as Albert had posted. Using the feature of the Package Wizard
included in the Visual Studio Tools Developer Extentions. My only concern was
the "#" symbol and whether it should be included. It SHOULD. I found a
reference to it during my searches.

Doesn't matter if the receiving machine has Office loaded (my target machine
did not ). The "keys" are for the Access application. As to how it would
affect the other users on the receiving machine, that would be determined
on/by the permissions of each user. I will be trying that on a machine that
has a "normal" user in addition to an administrator in a couple of days. As
long as they can run the app I think it should be O.K.

No way to do this via Tools/Options in Access although you could add these
entries using regedit on the receiving machine.

How I did it EXACTLY, because I'm lazy, is, I highlighted the info in
Albert's post and right clicked to copy. Then pasted it into a Word doc for
reference. Then after opening the package wizard and going to the page for
Registry additions I copied the text from the Word doc( making sure only to
copy the actual values ) and pasted them into the wizard form using Ctrl v
after clicking in the appropriate field.

ROOT:Local Machine .......is a ClickBox option.

SOFTWARE\Microsoft\Jet\4.0\Engines
SandBoxMode
#00000002 ( watch out for the " : " it likes to add itself to the highlite)


Software\Microsoft\Office\11.0\Access\Security
Level
#00000001

Worked like a charm. Hope this helped. No more warning messages on the
"receiving" machine.

 

[Guest]

nmghj