[AccessD] A2003 Macro Security in Runtime "issue"...

Get their network guy to change the following registry settings of the
following key, should help you change the security level of the macro in 
Access 2003. He should be able to change this globally across the 
network for each client PC, there is even a way to do this from Access 
VBA code using WMI with proper network permissions.

HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Access\Security\Level

If the value is 1, then the macro security of Access 2003 is set to low.
If the value is 2, then the macro security of Access 2003 is set to medium.
If the value is 3, then the macro security of Access 2003 is set to high.

WARNING: If you use Registry Editor incorrectly, you may cause serious 
problems that may require you to reinstall your operating system. 
Microsoft cannot guarantee that you can solve problems that result from 
using Registry Editor incorrectly. Use Registry Editor at your own risk.
--------------
or you could try this subroutine to execute on the runtime startup as 
toolbar menus are disabled by runtime methods

maybe after checking this is set. I forget the order of execution.
 Access.Application.AutomationSecurity = 1 ' msoAutomationSecurityLow

  This sub activates the Macro -> Security submenu to open
' the Macro Security dialog window for the user who is using
' the runtime version of Access '03 instead of the retail version,
' which may need to have the default security level changed in
' order to run the code in the modules.
'This sub requires the Microsoft Office 11.0 Library reference

http://www.access.qbuilt.com/html/vba.html#SetMacroSecLvl
-----------------
or
Sagekey has an Access 2003 MSI install script that avoids this but is $425.
----------------
or build your own security certicate but then you still have to install 
in users certificate pool

There are some easier ways but not if it is a runtime

Greg Smith wrote:

>Hello everyone!
>
>Is there a way to shut off the security messages you get in Access 2003 in
>a runtime version of an application?  I have them shut off on my computer
>and it works fine here, but when I have the customer install it on their
>computer(s) (they don't have Access installed at all), they get the
>messages on startup about unsafe expressions, etc.  They can't shut them
>off on their computers because the application doesn't allow access to
>those areas (restricted menus).
>
>I was hoping to be able to do it internally (in vb), but that's probably
>exactly what MS is trying to prevent with the security.  So far they've
>succeeded and I've failed...and turning warnings on/off doesn't do it
>either.
>
>Of course, if they have Access installed, I'll tell them to just shut off
>the macro security (set it to 'low')...which has it's inherent dangers,
>but in most cases is ok.
>
>Any help or suggestions would be greatly appreciated.
>
>TIA!
>
>Greg Smith
>gregsmith at starband.net
>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada