avoiding the need to set Macro security level to Low

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

I have built an application in Access 2003 that will be shared by multiple
users. However, I have noticed that in order for the application to run,
the users must set their Macro security level to Low (Tools - Macro -
Security - Low).

Is there anything I can do to my application, which of course contains VBA
code, to run while enabling the users to keep the macro security level set
to Medium?

Thanks in advance,

Paul
 
Thanks for the suggestion, Chris.

Question - I would think that I need to put the path to the front end
database in "full path to your db" instead of the back end database. Is
that true?

Paul
 
Paul said:
I have built an application in Access 2003 that will be shared by multiple
users. However, I have noticed that in order for the application to run,
the users must set their Macro security level to Low (Tools - Macro -
Security - Low).

Is there anything I can do to my application, which of course contains VBA
code, to run while enabling the users to keep the macro security level set
to Medium?

Thanks in advance,

Paul
Click to expand...
 
You can digitally sign the application with a certificate the user computers
will trust, or you can install the front end mdb to a trusted location
(don't remember for sure if this is supported in Access 2003- it's
definitely part of 2007). You can buy a code-signing certificate from Thawte
or any other certification authority accepted by Windows. I think price is
about $250/year.
 
FWIW, if it's going to be an in-house application, it's hard to justify
paying $250 per a year when one can just self-signed certificate using
either selfcert.exe or makecert.exe which are included in the Office
installation and have the end users computer set up to trust the
self-signed certificate.

For a public-facing application, OTOH, self-signed certificate wouldn't
be appropriate.
 
Back
Top