Adding & Removing License Keys
In a nutshell
Programmer keys (Developer, Engine, OEM) can only be installed into interpreted databases. These keys are physically written in the 4D structure file and stay there until they are removed. Interpreted structure files can safely be compiled — installed plug-in keys will still be there in the resulting compiled structure file.
End-User keys (Server Expansion, Runtime) should be installed into interpreted or compiled databases depending on their kind. These keys are physically written in the Escape folder, inside the 4D folder of the machine on which they are installed.
WARNING An error message saying that the kind of key is not applicable will be issued when attempting to install keys into a database that is not appropriate, e.g. programmer key into a compiled database.
Online activation of keys takes place when a key is first installed on a new machine. During activation, hardware identifiers of the machine are stored on Escape's activation server. User privacy is never put at risk in any stage of the activation procedure.
Demo mode is invoked when attempting to use the plug-in without a suitable license key. Demo mode will let the plug-in work for 30 minutes before restarting 4D.
The ELM (Escape License Manager) dialog
The ELM dialog lets review and modify all installed license keys of all Escape plug-ins. The dialog can be perused in both single-user and client/server.

To invoke the ELM dialog:
• In single-user: keep down CapsLock and Shift when launching the database.
• In client/server: choose Escape Licenses in 4D Server's Help menu.
Adding a key in single-user
There are two (ultimately converging) ways for doing this: you can either invoke the ELM and click the Add button on the Catalog page, or start using the database and wait for the plug-in to prompt you asking for a suitable key. No matter which method you choose, the procedure is the same.
Assuming you chose the second method, the first call to a plug-in method will cause the following alert to appear:

Click Demo if you don't have a license key, to use the plug-in in Demo mode. If you have a license key, click Install key to launch the wizard and install it.
Step 1 | ![]() |
Accept the license agreement to continue. Decline to abort the procedure. |
Step 2 | ![]() |
Carefully copy all lines of the license key from your delivery email and paste it into the entry area. When done, click Next to decode and validate the key. |
Step 3 | ![]() |
The key has been decoded and validated, and its details are now displayed. Make sure you are installing the right one. If this is not the right key, click Back to correct the mistake. Click Next to activate and install the key (an internet connection is required for activation). |
Step 4 | ![]() |
The license key has been installed and you are seeing the Catalog tab of the dialog. To install another key, click Add. When done, click Done to close the dialog. |
Adding & removing keys in client/server
In client/server the administration of license keys is done exclusively from the ELM dialog, which can be invoked from the 4D Server's Help menu, item Escape Licenses.
To start adding a key, click the Add button in the Catalog page of the dialog.
Where is licensing information stored?
Programmer keys (Developer, Engine, OEM) are stored in the structure file. The keys remain unaltered as the structure undergoes compilation, merging with 4D Volume, renaming, or even compacting.
End-user keys (Runtime, Server Expansion) are stored in a .QLC file that resides in the Escape folder inside the 4D folder of the machine (in c/s this refers to the server machine). The name of the .QLC file is based on the name of the database (using only the letters, not the numbers or other characters).