Access 2003 Runtime Security Warning

  • Thread starter Thread starter mbox204
  • Start date Start date
M

mbox204

Greetings,

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

Setup:
Win 2k Pro, SP4
Access 2003
Access 2003 Runtime Extensions
 
Hi.

The best way to get rid of the Macro Security warning every time the
database application runs is to create a Digital Certificate and sign the
application with this certificate. That way, the macro security settings
can be left at either medium or high.

If signing the application with a Digital Certificate is not an option, then
the destination computer can have the macro security settings set to Low to
avoid the three warning messages. One may do this by changing the Windows
Registry settings or with code that can be saved in a module in Microsoft
Access and later run on the computer. The necessary steps for the Registry
changes and the code (in both English and Spanish) are located on this Web
page:

http://www.Access.QBuilt.com/html/vba.html#SetMacroSecLvl

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Thank you for the response.

Not having used this feature yet, it appears I can create a Digital
Signature using the Custom Startup Wizard as part of the Access Developer
Extensions. It seems that creating my application for startup would then be
a two part process.
1. Run the custom startup wizard, obtain the digital signature are part of
that process
2. On completion of the custom startup wizard, incorporate the results into
the package and deployment wizard.
 
Hi.
Not having used this feature yet, it appears I can create a Digital
Signature using the Custom Startup Wizard

Sorry. I'm not familiar enough yet with the Custom Startup Wizard Add-in to
give instructions to others.

If you support Windows XP, make sure that you test your package with Windows
XP SP-2, because people are finding some unexpected problems with it, and
you don't want your customer encountering any surprises with your
application.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Back
Top