Using the New VBA Project Signing Feature in Access
OUTLINE:
This video explains how to use the new VBA project signing feature in Access. The feature is currently only available to those on a Microsoft 365 Insider Channel but will be released to the Current Channel in the near future. It will be particularly useful in organisations where the use of trusted locations is not permitted. It will also allow developers to ensure the code in their projects are not altered after the files have been distributed to clients.
The video explains how to obtain a code signing certificate and use it to sign your ACCDB/ACCDE files
It also compares the properties of this feature with the existing approaches of using trusted locations or trusted documents when distributing your Access applications
For further details and the example apps, see my article: https://isladogs.co.uk/vba-project-si...
Also, see another related article: https://isladogs.co.uk/trusted-location/
TIMES:
0:00 Intro - new feature allows VBA projects to to signed using a code signing certificate
0:40 Existing methods of adding trust to Access databases
1:28 VBA Project Signing feature - has always been available for MDB/MDE files. New feature is for ACCDB/ACCDE files and is currently only available as a pre-release version for those on an Office 365 Insider channel
2:33 Web article with 2 example apps for download (unsigned & signed)
4:20 DEMO - unblock downloaded file to remove the 'mark of the web' (MOTW) & setting Access macro settings
6:09 Enable Content security banner - click Enable Content to make database a trusted document
7:15 Run code with trusted document - very slow as antimalware scan (AMSI) runs when database loads and each time code is run
8:45 DEMO - code can be changed or action queries created/edited - code still runs - no protection against code being changed after distribution
10:15 Move file to trusted location - code runs much faster as AMSI scan no longer runs - file deemed safe to use
11:45 Trusted location also doesn't protect files against unauthorised changes after distribution
12:04 DEMO - attempt to use code signing certificate in older version of Access (2010) - FAILS - digital signature cannot be saved with ACCDB file
14:28 DEMO - setup Access 365 to prepare for code signing - change macro settings
16:10 DEMO - add code signing certificate to Access 365 project (Insider channel)
17:21 DEMO - client needs to trust publisher for code to run from untrusted location
18:24 Code runs quickly once signed, even from untrusted location
18:43 Effect of changing code - digital signature invalidated so code will no longer run
20:11 Using a self certificate for testing purposes only
21:55 BUG: Alter an action query invalidates signature but currently shows an incorrect message that the certificate has been tampered with
23:02 DEMO - creation of a self certificate using SELFCERT.exe
24:12 New code signing feature is more complex to use but adds additional protection
25:22 Summary of existing trusted document/trusted location options
26:20 Summary of new code signing feature
27:22 Related articles
28:16 Thanks for watching ... please like/subscribe & suggest topics for future videos