There's no two ways about it: you WILL run into problems. If your code is
not digitally signed, it will not run on a user's machine unless either
their macro security is set to low (which is strongly discouraged) or they
choose to allow the VBA project (which non-savvy users won't do, and which
is prevented on most corporate networks anyway).

To sign the project digitally you need to buy a certificate from an outfit
like Verisign, and you're then committed to renewing the certificate
annually. And, your users have to choose to accept your certificate. On top
of which, some corporate IT departments block feral code entirely, in which
case your code won't run whatever you do.


"Arlan" wrote in message
...
I am looking for a document to help me understand security issues for VBA
projects, so I don't run into problems when a user installs the
application.
A reference to a good document or two would be a great help.