Digital Signature is lost if SQL Server tables are relinked

[Thor_MN]

Has anyone run into this problem? I have a database that is used to
create reports from one of three different "company/division" SQL
Server databases. The startup form allows the user to pick which
backend database is to be used, then the tables are relinked if they
aren't already pointing at the chosen db.

This all works fine until they try to open the database again after it
has relinked - they get a message saying that "The code or macros in
this file do not match the digital signature."

It works fine on my PC as I have the certificate used to sign the code
on my PC. Am I wrong in thinking that this shouldn't be happening? I
know that the connection string in tabledefs have changed (the old
tables have to be deleted and corresponding new tables created) , but
the code has not changed in any way. Does the "Code Signing" also
cover the tabledefs? If it does, can anyone think of a way to keep it
from deciding that this is a hostile action and removing the signature?

If I'm going to be forced to decide between making separate Access DBs
for each company and not code signing, I'm going to be frustrated.

[david epsom dot com dot au]

Pathetic, isn't it? Not that I object to strong security, but
either they set the bar at the wrong place, or else they really
need a extra 'medium security' level which allows you ignore
changes to specific objects.

In any case, you may be able to get around this by putting
more of your link inititialization in a separate file.

That is, use a DSN.

Big improvement in security, right?

(david)
"Thor_MN" <sa***********@msn.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

Has anyone run into this problem? I have a database that is used to
create reports from one of three different "company/division" SQL
Server databases. The startup form allows the user to pick which
backend database is to be used, then the tables are relinked if they
aren't already pointing at the chosen db.

This all works fine until they try to open the database again after it
has relinked - they get a message saying that "The code or macros in
this file do not match the digital signature."

It works fine on my PC as I have the certificate used to sign the code
on my PC. Am I wrong in thinking that this shouldn't be happening? I
know that the connection string in tabledefs have changed (the old
tables have to be deleted and corresponding new tables created) , but
the code has not changed in any way. Does the "Code Signing" also
cover the tabledefs? If it does, can anyone think of a way to keep it
from deciding that this is a hostile action and removing the signature?

If I'm going to be forced to decide between making separate Access DBs
for each company and not code signing, I'm going to be frustrated.