Self Signed certificates are not intended for export. Note the following in
Access help for creating a self signed certificate: "Databases signed with a
self-signed certificate are recommended only for personal use, or during
testing and development phases of an Access solution."
I think you will find the hours you spend fighting this will have a higher
cost than purchasing a real certificate that you install on your computer.
Other users don't need the certificate. They don't even need to be in the
same location. The first time they are asked if they want to always trust
databases signed with the certificate.
Getting your first certificate can seem a bit complicated. Just make sure
you get the VBA flavor, not the EXE/DLL flavor. Also be sure to add the
timestamp to your registry. I use VeriSign, which is about $499/year. Scan
the other recent questions in Access Security. I noticed one one that costs
$99.
Good Luck.
EarlM
"rocco" wrote:
[Quoted Text] > Hello,
> after many nightmare about getting rid of Access security warnings popping
> up on computers of few members of our staff (all of them will use the runtime
> version of Access) that use an application developed with Access 2003 and
> deployed with the Package Wizard provided with the Acees 2003 Developer
> Extension, I come up with the need to sign my VBA project with a self-signed
> certificate. Fine.
> But after many trying...all unsuccessful...the database opens but many
> features still wont work (expecially many functions...). After few readings
> it seems I have to install the certificate on each pc's (which I
> did)...but... the certificat should be exported from my pc with the key, and
> it seems there is no way to have it done!
> The "do not export the key" option is check by default and it seems there is
> no way to change this choice.
> What can I do? I can I export the certificate WITH its key so that other
> computers can really trust my application?
> Thanks for any help...I'm kind of lost
|