3 Microsoft Access Protection Methods
QuickLicense supports three methods to protect a Microsoft Access file and restrict use to a licensed computer. Each method supports offline, online, dongle or floating license server activation using any of the supported license types (Trial, Product, Try/Buy and Subscription) and features. Pick the option that works best for your project.
1. EXE with Macros Enabled
This method wraps your ACCDE file into a protected EXE. It has been supported for several years and requires that Macros be enabled in the Trust Center and the full MS Access application resides on the customer computer.
Once activated, the EXE can launch directly into your Access file or present the Open Data File window to manage named instances of your Access file.
2. EXE with Trusted Data Folder
This method was introduced in 2019 and requires the full MS Access application on the customer computer. It wraps your ACCDE file into a protected EXE. Once activated, the EXE can launch directly into your Access file or present the Open Data File window.
The Data Folder holding your protected files is automatically included as a trusted location within Access by the EXE on first launch. The user is not required to enable Macros.
3. VBA Bound License
This method uses VBA code to bind your Access file to the QuickLicense runtime and your Ticket file that defines the license. Those files are stored at a fixed location on the computer during the App Install process. The VBA code pasted into your Access file is provided by the OfficeProtect product.
Your application is distributed as any type of Access file that supports VBA. There is no Open Data File feature. The customer computer requires either the full Access application or Access runtime (if your Access file supports that environment).
To learn more about this approach, see the Access API sample project. It includes an Access application and installer plus an Access API Example PDF and demonstration video.
Learn more about Protection and Licensing
for Microsoft Access or how to deliver your App with a Code Signed Installer