Thank you.

This process only signs the package the database is saved into, it does not sign the actual database. Is there a way to actually sign the database itself, so it can become a trusted document?

Hi Kirt. Did you open the accdb-file that you saved after opening the accdc-file? If yes, did you check if it was signed?

Very interesting. Forget this was available. But, guess I don't see the purpose of doing a Self Cert ... which is only good for that specific database ... on your specific system? What am I missing ? Also ... let's suppose you get a 'professional' Cert from that company. Then you distribute say to people in your company. Will this professional Cert ... avoid the Access Security message ... assuming you have not set Trusted Locations, and set VBAWarnings to 1 ? I have .BAT files that I manually run that set Trusted Locations and VBAWarnings for Access 2010, 2013 & >=2016 ... depending on what a user is running. This is a tedious process when it comes to some 400 users ... over time, that get new laptop and/or new versions of Office. I went down the rabbit hole again (it's been a long time) of ... trying to have (simplifying here) ... code within a db that ... checks for the version of Access, then for a specific RegKey under the Security section ... and if missing, write the Reg keys to set Trusted Locations (for our Org) and VBAWarnings to 1. Thought I actually had this working ... BUT is was fooling myself, lol. In the end ... it's a Catch 22. You cannot execute VBA code ... unless VBAWarnings is already set to 1 ... and/or Trusted Locations are set. SOOOO ... looking for some other possible way to do this.