Digital Signature Problem

[Dean]

I am upgrading an Access 97 mdb to a new version that will be used by people
with Access 2002 and 2003 and am attempting to assign my own digital
signature so that the 2003 users won't have to see the prompt if they have
their security set above Low. I applied the certificate using 2002, created
an MDE and when I open the file using 2003 I get a message that the
certificate is invalid or the code has been changed since signing. Any ideas
why this would happen? any ways to prevent?
TIA
Dean

 

[confumbled]

If you created the signature using the MS software, it is only valid on the
machine it was created on. You would need to create a certificate on every
machine using that database.

 

[Jack Ray]

I had the same problem. The database is on a network drive. Access is loaded
on my machine at work (C Drive) and a Metaframe server for working at home.
I downloaded the selfcert.exe from Microsoft and I signed the project on my
work computer. When I logged onto theMetafarme, it discarded the
certificate. I tried signing the project and then locking it. That did not
work. I tried locking it and then signing it; that did not work.

It appears that you can only sign the database once.

Do I have to download the selfsign on both the pc and the metaframe and sign
the project on each. Isn't the second signing going to overwrite the first?

Do I have to do anything in Internet Explorer on either PC?

Someone suggested setting up a macro to send keystrokes to select "ok" when
the security menu pops up. I would prefer getting the digital signatures
correct because I may be setting up other databases.


Jack