I have used the setup wizard to turn my mdb to an mde.
Then used the package wizard to create the setup.exe.
When I run the setup.exe on a PC without MS Office, it
installs fine. My question is when I run the mde with the
runtime of Access it gives me a warning.
"The file may not be safe if it contains code that was
intended to harm your computer. Do you wan to open this
file or cancel the operation?"
I thought installing MS Jet 4.0 SP 8 would help but it
didn't. Also when I created the mde I had my macro
security set to low. I get the same warning on my
programming PC when I open the mdb.
Any ideas?
Hi Val,
The warning you are seeing is caused when you open a database that has not
been digitally signed in a copy of Access that is using Medium or Low Macro
Security. This is different that the warnings related to Jet sandbox mode.
The Macro Security setting is specified on a computer, not in the database.
The setting on your development computer does not affect the setting on
other computers where the runtime components are installed.
One way to avoid this warning is to sign your database, which requires you
to have a digital certificate from a thrid party Certification Authority
such as VeriSign or Thwate.
A second way is to set the Macro Security on the runtime computer to Low.
Since the runtime componets do not include the standard Access UI, you
would have to programtically change this setting in the registry. One thing
that you need to be carfull of, these settings are part of another users
computers and affect all Access applications on the comptuer. If you decide
to change this setting on the computer, other Access runtime applications
will be changed also. It is also possible that you will not be able to
change the settings if those settings are part of a Global Policy that is
locked down by the system administrator.
A third alternative is to use an automation script to launch your
application via a stub program. In this scenario, your short cut would
point to either a script file or stub executable that would open your
application in an automation instance of Access and use the
AutomationSecurityLevel to reduce the level just for that instance. An
example of how to do this is documented at
http://office.microsoft.com/assistance/preview.aspx?AssetID=HP010397921033
&CTT=98. Use the link to show everything on the page and then scroll down
to the section on using automation to open a database under medium or high
security.
--
Regards,
Mike Wachal
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
