Digital Certificate Problem

[Guest]

I purchased a Digital Certificate from Thawte and applied it to my Access
2003 application. I've packaged my app with the Package Wizard and can
install on an End User's computer without any problem.

The problem is when the user opens the app the first time and tries to use
it, they receive the following error:
"You have modified a signed project. You do not have the correct key to
sign this project. The signature will be discarded."

Every time thereafter, when the user opens the app, they receive the
standard Security Warning. The one I'm trying to avoid in the first place.

My production PC is WinXP Pro SP2.

Any ideas?
Thanks,
Scott

 

[Paul Overway]

Is the app compiled? Are you distributing an MDE? Does this prompt come up
after your app has opened in Access or before, i.e., is your code actually
running when this happens? If after, what code are you running during
startup?

 

[Guest]

I've decompiled, compiled and created and MDE. When the app first opens, I
get a Security Warning stating, "This file has been digitally signed by [My
Company]. This file may not be safe if it contains code that was intended to
harm your computer. Do you want to open this file or cancel the operation?"
I select the box that asks "Always trust files from this publisher and open
them automatically", and then click Open.

The app opens; my Splash form opens and closes then stops on my Installation
form. Whatever action the user takes on this form, an entry is written to
the Registry. As soon as that happens I received the error, "You have
modified a signed project. You do not have the correct key to sign this
project. The signature will be discarded."

-Scott

 

[Guest]

I've traced the error to the following line of code:
DoCmd.CopyObject , "AutoKeys", acMacro, "AutoKeys_AP"

 

[Brendan Reynolds]

That would explain it - the MDB now includes a macro that it did not include
when it was signed.