Create digitally signed MDE files in Access 2007

[Chris]

How do we create digitally signed MDE files in Access 2007 ?

I tried to follow the procedure I was using in other office versions.

1. I installed the Verisign certificate (with private key).
2. Signed the MDB from VBA.
3. Create the MDE.

When I try to open the signed MDE, even on the developement machine
with
Verisign certificate (with private key), not only on test machine, I
get the
following warning: "It is not possible to determine that this content
came
from a trustworthy source. You should leave this content disabled
unless the
content provides critical functionality and you trust its source."

this secuirty notice does not give me the option for trusting my
certificate
as a trusted publisher.

Access macro security is "disable all macros with notification".

I selected "Disable all trusted locations. Only files signed by
Trusted publishers
will be trusted" but the problem is still the same. Singed MDB opens
ok, signed MDE is not ok. Is signed certificate been removed from MDE
files ?

My signed MDE's open (without certificate been checked) when I add my
program's directory in trusted locations.

Since my MDE's are signed, I shouldn't had to add my program's
directory in trusted locations.

Am I doing sth wrong in signing it ?

[Tom van Stiphout]

On 14 May 2007 22:16:54 -0700, Chris <CL*****@gmail.comwrote:

Your MDE is not signed. You can verify this using the Properties in
Explorer.

I would run the steps
1. I installed the Verisign certificate (with private key).
2. Create the MDE.
3. Signed the MDE from VBA.

-Tom.

>How do we create digitally signed MDE files in Access 2007 ?

I tried to follow the procedure I was using in other office versions.

1. I installed the Verisign certificate (with private key).
2. Signed the MDB from VBA.
3. Create the MDE.

When I try to open the signed MDE, even on the developement machine
with
Verisign certificate (with private key), not only on test machine, I
get the
following warning: "It is not possible to determine that this content
came
from a trustworthy source. You should leave this content disabled
unless the
content provides critical functionality and you trust its source."

this secuirty notice does not give me the option for trusting my
certificate
as a trusted publisher.

Access macro security is "disable all macros with notification".

I selected "Disable all trusted locations. Only files signed by
Trusted publishers
will be trusted" but the problem is still the same. Singed MDB opens
ok, signed MDE is not ok. Is signed certificate been removed from MDE
files ?

My signed MDE's open (without certificate been checked) when I add my
program's directory in trusted locations.

Since my MDE's are signed, I shouldn't had to add my program's
directory in trusted locations.

Am I doing sth wrong in signing it ?

[Chris]

Thanks a lot, Tom for your message.

Since my 2007 mdb (2002-2003 format) is signed, why the MDE I created
(using the MDB) is not signed ?

I haven't tried but could it be that only .ACCDB signed files could
create signed MDE files ?

[Tom van Stiphout]

On 15 May 2007 07:20:52 -0700, Chris <CL*****@gmail.comwrote:

I haven't tried all the combinations myself, but if you have some
time, please do and post back your findings here for others to enjoy.

The way I think about creating an MDE is that Access creates a new
file, and puts the compiled objects in it. But it does not take the
digital signature wrapper with it (nor should it - think about the
abuse that could ensue)

-Tom.

>Thanks a lot, Tom for your message.

Since my 2007 mdb (2002-2003 format) is signed, why the MDE I created
(using the MDB) is not signed ?

I haven't tried but could it be that only .ACCDB signed files could
create signed MDE files ?

[Chris]

The problem is that I don't have time :-(

I could never imagine this would be problem.

As in 2003, MDB files could be digitally signed and MDE files were
keeping the signature so clients could trust the MDE files. In 2007 it
seems to be different. I tried to create a ACCDB also and sign it, but
another file is created. If you try to open the new file created,
Access asks you to extact it in a new db.