• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1245
  • Last Modified:

Access 2007 - Notification on Close (Digital signature becomes invalidated)

I am making the transition to Access 2007, still running a 2003 database.  Every time I get into the database and add visual basic programming, compile, save and close the database, I get the following dialog box:
"Modifications to the database or project have invalidated the associated digital signature."

(See the attached image for the actual information box.)

I then have to reenter the database and reattach the digital signature.  What is causing this and how can I prevent it?

Access-Close-Error.jpg
0
shrimpfork
Asked:
shrimpfork
  • 4
  • 2
  • 2
  • +1
2 Solutions
 
thenelsonCommented:
First decompile and recompile the db in A2007.

1) ALWAYS CREATE A BACKUP OF THE DATABASE BEFORE DECOMPILING. (Just in case)

2) decompile: in run: msaccess "dbPathName.mdb" /decompile
   Compact/repair:  in run: msaccess "dbPathName.mdb" /compact
   compile: in VB editor: debug> compile
   Compact/repair
   http://www.granite.ab.ca/access/decompile.htm
0
 
shrimpforkAuthor Commented:
thenelson,
Just to be clear, my database is a 2003 version that I'm running in Access 2007.  Do your instructions still apply?
0
 
thenelsonCommented:
Yes
0
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

 
BitsqueezerCommented:
Hi,

I never used digital signatures but I would expect exactly this behaviour from an application which supports it. The signature should give the user the trust that the file is not modified in any way since release from the developer so if you as the developer change anything in the file you must create the digital signature once again. That's exactly what the error tells you in the message.
Further informations about digital signature for example here:

http://support.microsoft.com/?scid=kb%3Ben-us%3B832510&x=11&y=8

Cheers,

Christian
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
This is exactly what SHOULD happen, as Chrisitan has indicated. I use Digital Certificates in my applications, and any changes I make invalidates it, as I would expect.

The time to "stamp" your project is when it's time to deploy it ... you should never use a digital certificate during development, since ANY change to the codebase (even just opening a form or report in design view) will invalidate it.

So make your changes, get your file ready to deploy and then - as the last step before packaging - go to the VBA Editor and sign your project.

0
 
shrimpforkAuthor Commented:
Interesting.  I never saw this behavior in Access 2003 with the same digital signature.
0
 
shrimpforkAuthor Commented:
thenelson,
Just for kicks I tried your suggestion.  No change with this behavor.  I would be surprized if it did change it according to the comments from Bitsqueezer and LSMConsulting.
Jed
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
<Interesting.  I never saw this behavior in Access 2003 with the same digital signature.>

I use 2003 almost exclusively, and while I don't recall seeing the message, it definitely invalidates the signature.
0
 
shrimpforkAuthor Commented:
Bitsqueezer,
You mentioned that you don't use digital signatures. How do you get around the security warning when you startup the database?  Our databse is only for use in house and I personally hate dealing with digital signatures.
-Jed
 
0
 
BitsqueezerCommented:
Hi Jed,

I deploy Access databases only in house, too, using the Access 2007 runtime. On some PCs it display the warning, on others not - but it is only one click more for the user, it's his problem...:-)
It is not so important in my eyes because similar messages are displayed with macro enabled Excel files so the users knows this kind of message and how to handle them.

Moreover you can add trusted locations for your database, this helps surpress such messages. Examples you can find here:

http://www.accessribbon.de/en/?Trust_Center:Trusted_Locations

There are explanations and further links on the page (German site but the link is the English version).

Happy new year,

Christian
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

  • 4
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now