Question regarding certificates & converting to 2007

[Acie]

I'm currently converting an existing Access 2002 application to 2007. So I
converted my .mdb file to a .accdb file. (It seems to work fine in '07.)

To sign it w/ digital certificate: I did..
I opened the .accdb file (with Shift-key), and went to Ribbon -> Publish ->
Package & Sign and chose to create an .accdc file.

When I clicked on the .accdc file, I got a dialog box with the title of
"Extract Database to..." and prompting me to select a file to save as a
..accdb file.

My idea was to create a batch file (.bat) to e-mail to users for them to
click on run to create a shortcut to the Access Application. However, the
signed database with .accdc extension prompts the user to extract a file...
I'm confused..

Any ideas how to create a signed application to distribute to the users.

thanks,
Acie

 

[Brendan Reynolds]

I'm currently converting an existing Access 2002 application to 2007. So
I
converted my .mdb file to a .accdb file. (It seems to work fine in '07.)

To sign it w/ digital certificate: I did..
I opened the .accdb file (with Shift-key), and went to Ribbon ->
Publish ->
Package & Sign and chose to create an .accdc file.

When I clicked on the .accdc file, I got a dialog box with the title of
"Extract Database to..." and prompting me to select a file to save as a
.accdb file.

My idea was to create a batch file (.bat) to e-mail to users for them to
click on run to create a shortcut to the Access Application. However, the
signed database with .accdc extension prompts the user to extract a
file...
I'm confused..

Any ideas how to create a signed application to distribute to the users.

thanks,
Acie

The last time I looked at this was during the beta, so I can't be completely
certain that nothing has changed since, but at that time, you could only
sign the *package*, not the application. To run your application, the user
had to extract it from the package, as you describe, and the extracted
application was unsigned.

Taking into consideration this issue, the fact that the warning message a
user sees when they open a signed app isn't any less alarming and confusing
to the average user than the message that they see when they open an
unsigned app, and the whole certificate-expiration time-stamping mess, I
decided that I could no longer justify spending a couple of hundred Euro
every year on a certificate, and declined to renew mine when it expired.