D
Dale Fye
Posted this about a week ago, and never got a response. Am hoping an MVP
might pass this on to someone at MS for an answer.
I've been using A2007 for several months now, and really need to resolve an
issue with digital signatures and the trusted publisher.
When working in A2003, all I had to do was digitally sign my mdb or mde, and
my users could elect to save the file to a trusted location, or add me to
their trusted publishers list.
Now, when I try to digitally sign an accdb, I get a message to use the
Publisher, which creates an accdc file, which is digitally signed.
However, when my users get this accdc file, and open it, it asks them to
extract the accdb file to a location on their system. Unfortunately, this
accdb file is not digitally signed, so every time they go to open it, they
are presented with the Options button. Unfortunately, my govt client
recently implemented procedures to prevent users from having trusted
locations, so now there doesn't appear to be a way to provides my
application users with a digitally signed copy of the file, which they could
setup to "trust the publisher".
If I convert the file to an accde, I have to enable macros before I make the
conversion. But when I do that, the file still is not digitally signed, so
when the users open it, it presents them with the "A potential security
concern has been identified" dialog box.
Is there any way to digitally sign the accde file so that all the users have
to do is accept my signature as a trusted publisher?
might pass this on to someone at MS for an answer.
I've been using A2007 for several months now, and really need to resolve an
issue with digital signatures and the trusted publisher.
When working in A2003, all I had to do was digitally sign my mdb or mde, and
my users could elect to save the file to a trusted location, or add me to
their trusted publishers list.
Now, when I try to digitally sign an accdb, I get a message to use the
Publisher, which creates an accdc file, which is digitally signed.
However, when my users get this accdc file, and open it, it asks them to
extract the accdb file to a location on their system. Unfortunately, this
accdb file is not digitally signed, so every time they go to open it, they
are presented with the Options button. Unfortunately, my govt client
recently implemented procedures to prevent users from having trusted
locations, so now there doesn't appear to be a way to provides my
application users with a digitally signed copy of the file, which they could
setup to "trust the publisher".
If I convert the file to an accde, I have to enable macros before I make the
conversion. But when I do that, the file still is not digitally signed, so
when the users open it, it presents them with the "A potential security
concern has been identified" dialog box.
Is there any way to digitally sign the accde file so that all the users have
to do is accept my signature as a trusted publisher?