License File Expiration Fields Tab

image\Lf_exp_shg.gif

Overview

With the exception of the Product Definition EZ Trial parameters, this tab contains most of the expiration-related variables.  Upon creation of a new License File, the Last Used Date and ime fields are updated with the current system date and time. This timestamp is also updated whenever the License File is saved if the option is enabled in the Tools / Options dialog box.

There are several date field shortcuts described in the Date Field Shortcuts section.

Expiration Type

This field contains a one-character flag representing the state in which the application should run. Refer to Expiration Types for a list of the types and their meaning.

Expiration Count

When the Expiration Type field is "E", the Execution count and Execution limit fields are used as counters to gauge when the application has exceeded its licensed functionality. Using the DLL/LIB interface, the Expiration count is incremented using pp_countinc() whenever the application has been executed or has performed whatever action is being counted. Using the ActiveX interface, the property ExecutionCount can be read and/or manipulated.


CAUTION:  When using the EZ Trial algorithm, care must be exercised to NEVER set the Expiration Count to the same value as the Execution Count.  Execution Count is managed by the EZ Trial algorithm in a special way.


Expiration Limit

When the Expiration Type field is "E", the Execution Count and Execution Limit fields are used as counters to gauge when the application has exceeded its demo functionality. The Expiration Limit field is generally set by LFEdit prior to shipping the software or can be remotely changed using Trigger Codes.

The EZ Trial engine uses this field to determine how many executions are left on this demo installation.  This counter is decremented automatically during startup until the value reaches 0.  If this value is -1 (negative 1), an unlimited number of executions will be permitted.  Also, refer to Times to Run parameter.  LFEdit initially sets this parameter to the same as Times to Run when saving a License File.

Soft Expiration Date

The Soft Expiration Date is generally used when a demo should be set to expire within a specified number of days after installation.  Refer to Soft Versus Hard Expiration for more information.  This field is only used when the Expiration Type field is "D", "P", or "S".  When one expiration date is required, the Hard Expiration Date must be used and this date should be left to 0/0/0.  When using the EZ Trial engine, this value should be left at 0/0/0 and the engine will initialize the value to the appropriate number of Days to Run.

Hard Expiration Date

The hard expiration date is generally used as a hard limit expiration date where the software will NOT run after this date with no exceptions. This field is only used when the Expiration Type field is "D", "P", or "S".  When one expiration date is required, this field must be used and the Soft Expiration Date field is left to 0/0/0.  When using the EZ Trial engine, a non-zero value must be placed in this field, even if the value is 12/31/2050.

Users Current

Used when limiting the number of LAN users in a network-based application. This field is generally used in Network Fixed Licensing, where the value is incremented automatically when a new user has been registered automatically with the ACTION_AUTOADD flag of the Copy Protection Check function or method.

Users Allowed

Used when limiting the number of LAN users in a network-based application. This field is used in both Network Floating Licensing and Network Fixed Licensing.

Installations Used and Allowed

These two numeric variables can be used to restrict how many times a particular application can be installed, or any other purpose.

Last Used Date and Time

The License File contains the Last Used Date and Time fields for two (2) purposes.  First, it is used to verify the user has not turned their clock back.  Using the DLL/LIB interface, the Last Used Date and Time is recorded by pp_upddate() when your application exits or during the execution of any other critical action.  It is tested using pp_valdate() at the start of your application. The ActiveX interface automatically tracks this information when the control is loaded and unloaded.  If the date has been turned back, the event ClockTurnedBack is fired.  The method ResetLastUsedInfo can be used to force the date to be updated, in the event the user inadvertently turned his clock forward, ran your application, and then turned it back.  Second, these fields determine the most recent License File when using License File Aliases.