6) Adjust Load Script

PLEASE NOTE: This step is only necessary if you wish to protect the load script functionality of your QlikView application. If not then you can proceed to the next step.

At this point you should note the contents of the auto generated load script snippet which you added into your application. Much of the script is involved with reading values from the licence file (if it can be located) and allocating these values to QlikView variables which you can subsequently use in your application if needed.

The important point to notice is the lower section of this auto generated script, a section of which is illustrated below:

Here, as the application developer, you need to decide if and how you wish to run the load script based on the success or otherwise of the check which preceed it. You will see a number of the following entries which you can pay particular attention to:

The results of the licensing check are made available through a number of QlikView variables, some of which you can see tested and checked for in the above screen shot. Click here for tables highlighting the most important QlikView variables and error codes supplied by QVGuard.

The default pasted example, as highlighted above, causes the script to exit if the licence check fails. However it also illustrates how, if the licence check does pass, that a different load could be executed if the 'Is Trial Version' flag has been set in the licence file.

It is up to you as the application developer to use the results of the licence check as you see fit.

Notice also in the above how QVGuard allows you to easily display a message box to your users with the following syntax:

let = QVG_ShowMessage('MESSAGE TEXT');