How do I digitally sign an Access 2K MDE file?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a large Access 2000 application that runs well under Access 2000 and
Access 2003. However, every time it is invoked under Access 2003, it causes a
warning message relating to possible malicious macros, etc. Supposedly, if
the application has a digital signature, the user can approve this signature,
and prevent subsequent displays of this warning message.

I have been unable to locate any information on how to accomplish this task.
Any and all help is greatly appreciated.
 
Jumping in here (because I can not see the OP's post):

OP, if your database uses the default workgroup information file, ie.
you do /not/ start it from a shortcut using the /wrkgrp switch, you can
easily suppress the A2k3 warnings by using the AutomationSecurity
property. Google this group for posts from me (TC) containiong that
word.

HTH,
TC
 
Fred,
Thank-you for the link to the CSD page. That got me started in a
meaningful direction, which is more than I can say for the MSDN library
search <g>. Just a note on the first CSD link (microsoft.com/resources.....).
That link is now rerouted to an Office 2003 SP2 download request page.
-- Jim March
Normal email: (e-mail address removed)
 
Are you the poster who started this thread? (I can't see the original
posts, for some reason). If so, is your database secured? If not, just
use the AutomationSecurity property to suppress the warnings.

HTH,
TC
 
TC said:
Are you the poster who started this thread? (I can't see the original
posts, for some reason). If so, is your database secured? If not, just
use the AutomationSecurity property to suppress the warnings.

HTH,
TC

TC, yes, I started this thread. The original post read as follows:
Click to expand...

I have a large Access 2000 application that runs well under Access 2000 and
Access 2003. However, every time it is invoked under Access 2003, it causes a
warning message relating to possible malicious macros, etc. Supposedly, if
the application has a digital signature, the user can approve this signature,
and prevent subsequent displays of this warning message.

I have been unable to locate any information on how to accomplish this task.
Any and all help is greatly appreciated.
-----
More specific to your immediate question, is the fact that the application
is a commercial product going into small businesses that frequently have
trouble understanding any installation or execution instructions beyond
"double-click here and follow the prompts". To allow ease of upgrades and
patches, the data tables are separate from the code, and both are protected
only by virtue of being MDE files with all of the startup options turned off
(as defined in Access 2K). The code initialization routine dynamically
creates links to the data tables as needed.

The installation process uses the setup.exe and setup1.exe code defined in
the Deployment Wizard included in the Office 2K Premium package. Examination
of that VB source code reveals that it only checks on the presence of Office
2K or the presence of Access Runtime (ART) to support the installation. Many
clients now have Office 2003, and I would like to take advantage of its
presence (rather than installing the ART in support of my application).

As earlier described, if I, knowing the presence of Office 2003, merely
setup a shortcut to the application, I always get the "macro warning..." box.
Given the sophistication of my client base, I cannot have that box repeatedly
displayed. It appears that the most reliable method of suppressing it is to
have a digital signature on the executable MDE file, and instruct the client
to accept it the first time. If you still think this is not the BEST way to
proceed, I'm always open to other suggestions.
-- Jim March
 
As I have already said: if the app is /not/ secured with Access
user-level security, just google this group for posts from me (TC)
containing the word automationsecurity. This will tell you how to
suppress the warnings, /without/ a digital certificate, in about 5
lines of code.

HTH,
TC
 
Back
Top