a) Depending on the scenario Disabling the security warnings and prompts may or may not be an option.
b) Disabling the security warnings and prompts in any event is not professional and would have to be done for every installation of the database.
To answer the OP's questions -
1)You would need to generate a code signing certificate (one where the intended use is set to code-signing)
2) I am not aware of any "simple" apps which do this. OpenSSL is a package which is far from simple but can do just about anything where certificates are concerned.
3)Once signed, a database will be signed for good. Every time the vba code changes, the database will need to be re-signed.
4) see below.
One thing to bear in mind where self generated certificates are concerned is that any certificate generated in this way will not be trusted - it will likely generate more security warnings and as Albert D Kallal says, is a "big waste of time".
The professional way of signing the VBA project in the database and thus removing the security warnings would be to purchase a code signing certificate from a certificate authority that is widely truted (e.g. Symantec / Thawte etc)
However, these certificates can be very expensive.
Signing the VBA in an Access project is actually very easy once you have the certificate installed.
For MDB / MDE
- Press Alt-F11 to bring up the VBA editor.
- Press Alt-T for tools, then Alt-D for Digital Signature.
- Click on the Choose button and choose the required certificate (you may need to import your cert into the personal certificate store)
- Click OK to dismiss the Dialog and OK again.
- Press Alt-F and choose Close.
your database's VBA is now signed.
For accdb / accde
1. select the File Tab,
2. Select the "Save & Publish" menu item.
3. Under 'Advanced", double click on the "Package and Sign" entry.
4. Select your certificate and click OK
5. Choose where you wish to save the signed copy of the database.
your database's VBA is now signed.