Serving the Business Basic market best

Besides to protect your programs with a password, there is also the possibilty to protect your application with a Dealer Activation Key.  When the activation file contains the correct key that corresponds to the dealer number, stored in  your program, only then your programs will be executed.  To be able to generate such a key, you need to buy a 'dealer key kit', and it consists of 3 items: 

1) You will receive a key generator program with which you will be able to generate your own dealer keys.  (an executable for 13/32 bit and a DLL for 32/64 bit environments)

2) You will also get an identification file.  This (small) file is used by the generator to create a unique key.  You may never change this file once you started generating dealer keys.

The key generator can produce 2 kind of keys:  developer keys and runtime keys.

• A developer key is used on the developing computer to be able to SAVE, EDIT and LIST your programs.
• A runtime key is used on the end-users computer to run the software that is protected with a dealer key.    During the this process, one can add extra options to the runtime key to enable LIST and/or EDIT.

The keys are based on the 'system id' of the machine and are therefore different for each computer.

3) You will also be assigned a unique package number.   To add the above keys to the activation file, you use the normal activation program:  pvxwactv.exe (windows) or pvxactv (linux/unix). 

After the activation is done with the 'dealer key' package, programs kan be saved and protected with the command  SAVE "program",OWN={unique package number}.   If you want to protect all of your programs with the dealer key, you can set parameter 'OW'={unique package number}.  Now, every program gets the dealer key when it's saved, even if you save it without the OWN option.

The developer also has the ability to assign 25 different flags, and each of them can be added to a program by means of  SAVE "program",OWN={unique package number},FLG={1{:2{:3{:.....{:25}}}} }. For example, programs from the group 'general ledger' can be assigned FLG=1.  Programs from the group 'account payable' can be assigned FLG=2, etc...  Only runtime licenses generated with the correct flags can execute these programs.  ie. A runtime license, activated with flags 1:3, will not be able to run a program saved with FLG=2.

For information about the price, please contact our sales department.