ACF-Plugin 1.7.7.0 : More Flexible License Registration
In this context, registering means activating the license inside the plugin only. No information is sent “home” — it simply enables your license locally.
There are two types of licenses: Developer and Runtime. These are usually bundled together in the same license key. Traditionally, you would place a “Set Variable” script step in your startup script that contains the ACF_RegisterPlugin calculation provided in your license email.
From version 1.7.6.5, the plugin now also saves the license on your computer. When the plugin starts, it checks for this file, and if it exists, it automatically activates the license. This means that on your own machine, you no longer need to call ACF_RegisterPlugin explicitly. This automatic saving and activation is applied only for developer licenses.
Update 1.7.7.0: We have added a plugin preference dialog available from Settings->Plugins->Horneks ACF-Plugin->Configure.
In this dialog, you can see license info, and browse installed ACF-packages and their functions. Function prototype both when calling from FileMaker calculations, and from other ACF functions. NOTE: licenses bought in our license shop is always perpetual, i.e. they dont expire. I am internally using a shorter expiration date for demo purposes.

Developer License Installer (ACF_DevLicense.fmp12)
To simplify developer license installation, we provide a small FileMaker app called ACF_DevLicense.fmp12. This tool is available in the download area and allows you to paste the license string from your license email and register it with a single click. The license will then be saved securely on your computer and automatically activated each time the plugin loads.
The location of the license file is:
~/Library/Application Support/ACF/license.acflic
The file is bound to your computer, encrypted with data from the license key applied.
Different scenarios
Several runtime users and one or more developers using a server-hosted FileMaker application
- Runtime users: The app can include an
ACF_RegisterPlugincall with a runtime-only license. These users will not be able to compile source code, only load and execute ready compiled code. - Developers: Their developer license is installed locally on their computer (via
ACF_DevLicense.fmp12or manually) and will take priority over any runtime-only license used by the app.
Stand-alone applications (in-house or at client site)
Use ACF_RegisterPlugin with the required license type or install a developer license locally.
Distributable demo applications
Do not include an ACF_RegisterPlugin call. Development will use your locally installed license. Without a license, the plugin will run for 30 minutes in demo mode. Time-limited demo licenses are available from us on request.
