2003 Runtime Access message

[JRF]

Recently I have created a standalone Access application with Runtime version
of Access through Package and Deployment wizard, FE/BE application.
Everything went well for this however, when I launch the application FE, a
message appears regarding macros, "some macros may harm your computer.... do
you wish to continue..."

I answer yes and the application opens and works like it should. Macros
within the FE are menu bar items created specific to the application. Am I
missing a setting in the package and deployment wizard, or do I need to code
something into the FE? It would be nice to eliminate this message from the
start up. Understandably, I do not get this in the full Access version when
launching this application, as I have disabled the macro warning message in
Macro/Security.

Any suggestions are appreciated, other group posting etc...

Window 2000 Pro
Access 2003
Runtime Extensions


thanks.

 

[Albert D. Kallal]

You can either get a signed certificate, or do as you did with your full
version..set macro security to low.

You can in fact include the macro security menu in the runtime (I done
this..and it works).

On the other hand, you can set JET to sandbox mode for everything else but
ms-access, and macro security code to low

Simply add the following keys to your runtime packing (the package wizard
does have provision for adding 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 of 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....

 

[Craig Alexander Morrison]

Edmonton, Alberta Canada

Simply add the following keys to your runtime packing (the package wizard
does have provision for adding 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

Albert have you tried them? I have and they are not accepted, you get error
messages during the installation.

Perhaps something else has to be done, perhaps you could let us know in what
circumstances this works.

This problem appears when logged on as an Administrator and on both WinXP
SP2 and Win2000 SP4.

I have added the menuitem on the runtime applications to allow the users to
change the setting.

I have to say that I would have thought that changing these settings may
require the User to do them explicitly otherwise the settings afford little
added security if an installation package can alter them. I may be wrong and
I am still waiting for more information on this from Microsoft.

 

[Albert D. Kallal]

#00 00 000 1

Albert have you tried them? I have and they are not accepted, you get
error messages during the installation.

Hum, I do it all the time. We are talking about the a2003 package and
deployment..right?

You sure you got the above values correct? You have to enter the values as
#00000001 in the p&d wizard . With some spaces, that is 7 zeros:

#00 00 000 1

I made quite a few runtimes with a2003. Some have sp2, some don't. Some have
JET SP8, some don't.

NONE have had trouble installing the runtime..and NO nag messages appear
when the application is launched with the above settings.

Perhaps something else has to be done, perhaps you could let us know in
what circumstances this works.

This problem appears when logged on as an Administrator and on both WinXP
SP2 and Win2000 SP4.

Hum, I only had the installs go on windows XP boxes, and never tried them on
win2000. As mentioned, some were windows SP2, some where not. And, also,
some where NOT JET SP8. (all of my installs worked).

I have to say that I would have thought that changing these settings may
require the User to do them explicitly otherwise the settings afford
little added security if an installation package can alter them. I may be
wrong and I am still waiting for more information on this from Microsoft.

I agree. But then software would have to change the settings in the
registry. On locked down machines users can't do this. (yes..my installs are
being done by people with admin prev). However, for some of my clients users
of each windows XP box are NOT admins..and you can't even install a mdb/mde
into the c:\Program Files\ directory anymore (since all program dirs are
read only in many companies that lock down pc's real good). So, that caused
problems since the files were read only, and often I could not "update" a
new front end via winzip (that is after the runtime has done its job). So,
then I then started using:

C:\Documents and Settings\All Users\

Well, it turns out a lot of companies have locked down the above dir also,
and again, the above is read only, and again oven winzip etc. can't update
to that dir. So, now I don't use c\Program Files, or c:\Documents and
Settings (both of which the p&d support). I have now gone back to making my
own dir like:

c:\MyCoolAccessApp

That way, I can have read/write files for non admin users. (these last
issues are not relevant to the nag messages and the reg keys..but I thought
you might like to learn some of my hard lessons with the a2003 runtime).

 

[Craig Alexander Morrison]

(these last issues are not relevant to the nag messages and the reg

keys..but I thought you might like to learn some of my hard lessons with
the a2003 runtime).

Thanks a lot for that we only have 97 and 2002 deployed at the moment and I
am currently working on something that may have a very wide distribution so
I am am only too happy to hear the issues that other have had.

As to the Package and Deployment settings I will check them to see if they
are in the required format, I hope they are not and that will be another
issue off the list.

I take it it is not just me but Access 2003 seems to be the best version of
Access being in effect the second minor upgrade from 2000.

 

[Craig Alexander Morrison]

Albert

#00 00 000 1

I have them entered as #00000001 and #00000002 and they kick it out it may
be something else.

I take it you do not mean they should be entered with the spaces?