## QPix v3 | ## Introduction

# Adding/Removing plug-in 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 forever, until removed. Interpreted structure files can safely be compiled -- the installed plug-in keys will still be there in the resulting compiled structure file. An error message saying that the kind of key is not applicable will be issued when attempting to install programmer keys in compiled mode.

- End-User keys (Server Expansion, Runtime) can be installed into interpreted and compiled databases. These keys are physically written in the 4D/Escape folder of the machine on which they are installed.

Adding a license key in single-user

The first time a plug-in command is called by the application, the plug-in examines its licensing status. If a license key is needed for normal operation, a dialog will be displayed requesting the missing license key (or the plug-in will run as demo). The dialog may request a developer or a deployment license key, based on what is missing in each case. Here follows an example with a missing Developer key:

# Step 1 By clicking on Demo, QPix will run for 30 minutes in demo mode. If you have a license key at hand, click on Install key to launch the wizard. After accepting the license agreement, you will proceed to Step 2 with the following dialog will appearing. | # Step 2 Copy the entire license key from your delivery email and paste it into the entry area, as prompted. When done, click on Next to decode and validate the key.

# Step 3 The license key has been decoded and validated, and its details are now displayed in the dialog. Review the details of the license key to make sure you are installing the right one. | # Step 4 The license key has been installed. Click on Cancel if you are done. Click on OK to install more keys into this database. The procedure is identical for all types of keys, of all Escape plug-ins on all platforms.

Note: The keys that you are going to install do not have to correspond to the current platform or the current plug-in. For example, you can install here all the developer keys that your database needs: any plug-in, any plaform. Eeach will be used when needed.

Escape Licenses Manager: the control panel for plug-in license keys

You can review and modify the license keys of all installed Escape plug-ins through the Escape Licenses Manager (ELM). In single-user the ELM window can be invoked on startup of the database, by keeping CapsLock and Shift down.

In single-user the ELM window looks like this:

License keys are divided in two groups:

- Programmer keys are those maintained by the programmer: Developer keys, Engine keys (unlimited Runtimes) and OEM keys.
- End-user keys are those maintained by end-users: Runtimes and Server Expansions.

Adding/Removing keys in client/server

In client/server all license key administration is done from the Escape Licenses Manager that is accessible from the Escape menu in the server's menu bar. In client/server the ELM window has a second page that shows dynamically the seat usage of Server Expansions.

In client/server the ELM window looks like this:

Where is licensing information stored?

Programmer-supplied keys (Developer, Engine, OEM) are stored in the structure file and they stay there until removed by the programmer. License keys remain unaltered as the structure goes through compilation, merging with 4D Engine, renaming, or even compacting with 4D Tools.

End-user-supplied keys (Runtime, Server Expansion) are stored in a .QLC file that resides in the Escape folder inside the 4D folder. The name of this file is produced based on the name of your database (just the alphanumeric characters).