ji********@compumarc.com wrote:
Paradigm wrote:
I distribute some Access 2K applications as mde files using the Access2K
runtime.
Now that I am thinking of updating to Access 2003 I find that, when I launch
an mde file, I get a number of warning messages about macros and security
which are a nuisance to the users.
Is there any way of avoiding these messages?
Alec
What I do is use selfcert.exe to create a digital signature that can be
applied to the mdb file. Another twist I came across recently was that
for a certain machine I had to run mmc (Microsoft Management Console)
using the Add/Remove Snap-in option to drag and drop the digital
signature into a Trusted Certificates category. So far I have been
able to get rid of all the warnings. Only a few machines have needed
the digital signature fix so I create the digital signature with the
user's name. I haven't had to do this in a more automated way yet. I
hope this helps.
James A. Fortune
James, you have selfcert.exe generated certs to work on PCs other than the one the cert
was generated on? That's not supposed to happen...
The "proper" procedure is to get a cert from a Certificate Authority but the cost/process
may be unreasonable for some applications.
There are work arounds ranging from modifying registry settings (that is considered rude
to do to a customer/client without their approval) to using Automation to start Access and
modify the security settings for the immediate session.
If you search this group on "macro security 2003" you should get lots of info.
--
'---------------
'John Mishefske
'---------------