Hi,

we are developing a piece of software which comes as an Access 2003/2007 mde
file which contains the program code. Those files are digitally signed in
Visual Studio using a code signing certificate. This basically works fine
except for the fact that now and then the signature of those files gets
corrupt and users see a "Microsoft Access Security Notice ... A potential
security concern has been identified. Warning: The digital signature has been
tampered with after the content was signed. This content cannot be
trusted...".

I cannot find out which event causes the signatures to get corrupted, but it
happens now and then and it happens to most of our customers. Anybody got any
idea?

Kind regards,
Dagmar

Dagmar <(E-Mail Removed)> wrote:

>we are developing a piece of software which comes as an Access 2003/2007 mde
>file which contains the program code. Those files are digitally signed in
>Visual Studio using a code signing certificate. This basically works fine
>except for the fact that now and then the signature of those files gets
>corrupt and users see a "Microsoft Access Security Notice ... A potential
>security concern has been identified. Warning: The digital signature has been
>tampered with after the content was signed. This content cannot be
>trusted...".

One possibility I've heard of is if an action query gets changed by
your code.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/