Here is a recent post by MVP Brendan Reynolds on this
subject:
If you are developing databases for your own use, you can
ignore it, you can set security to Low (Tools, Macro,
Security) or you can use the makecert.exe utility to
create a digital certificate that will be valid only on
your PC and use that to sign your Access files. You
probably have makecert.exe somewhere on your PC, but if
not it can be downloaded at the following URL
....
http://www.microsoft.com/downloads/details.aspx?
familyid=2B742795-D0F0-4A66-B27F-2A95FCD3425&displaylang=en
(Watch out for line wrapping on that link)
If you are developing in-house applications, talk to your
administrator. Using Certificate Server on Windows
2000/2003 Server, an administrator can create a
certificate that will be valid across the domain.
If you work for a company that develops applications for
third parties, your company needs to purchase a digital
certificate from a Certificate Authority (CA) such as
VeriSign or Thawte. If you're a private individual who
develops applications for third parties, you are, for the
time being at least, out of luck. In theory, there are
supposed to be 'Class 2' certificates for individual
developers, but in practice, they are unobtainable, as no
CA currently sells them.
I'm currently pursuing this matter with a CA who *may* be
willing to sell certificates to individuals in some
circumstances, and will post here when I get their answer,
but it could take some time. While the CA in question
answers technical questions promptly, they are very slow
to answer policy questions like this.[/QUOTE][/QUOTE][/QUOTE]
Also, here is some helpful advice from someone at
Microsoft:Within the Microsoft Access help topic "Digital Signature"
it details how to sign your database.
Regards,
Eric Butts
Microsoft Access Support
Hope that helps,
