Hi All,

How I did the VFP copy protection:

I have a VCX class to drop to the application

When Application is started VCX class check out the registration status of current app, if not registered there is a bunch of possibilites what happens next (it depends how VCX is configured - many possibilites to configure)
- It works fully only some defined amount of days (0, 14, 30, 60 etc.)
and then:
- No output to the printer is allowed
- Only N-records per table is allowed
- No saving is allowed
- No config chancing is allowed
- App stop workin totally but informing you with the register now window
- Etc. and other difficulties to boost to buy fully license

How licensing the app is done:

VCX read some spesific hardware / software dependendent information from your LOCAL PC / LAN Server and makes a 256 bit or more crypted "meta-key" from that infromation (meta-key can be invisible like with windows XP-registration or visible as with some 3rd party win applications). Then when you want to register (and pay :))) ) you VFP app:
- meta-key is sent to my (i.e. the seller of that copy protected app) registration server for a primary-key (invisible type) OR
- meta-key is readable from VCX generated registration window. Then you send it to my registration server or my registration email (what is BTW red automatically by VFP)

In both cases after a registered payment, you get the Primary key in a format like XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (what is "coincidentally" same fromat than MS uses). Primary key is then fed (automatically - invisible type or manually) to the VCX which then register the APP for a fully working mode.

If PC-HD / Server-HD is corrupted / spesicif software / hardware is changed and app doesn't work fully anymore, new primary key is sent for a new meta-key (which is generated again if spesific hardware/software profile is changed).

If APP is removed from current PC and moved to another PC, VCX stamps old PC so that APP doesn't work there anymore without a new license. This is handy when you sell spesific amount of licenses and license is moved to another PC.

Also 256 bit or more crypted "meta-key" generation algorithm is user-definable within that VCX. windows API/VFP FFC library can be used for that encryption.

Other copy protection VCX capabilities:
- it handles APP new version update process too if needed from some defined internet IP to your local / LAN PC

This is quit a safe method for a copy protection because VCX can be configured which hardware and software parameters it reads and how the meta-key is crypted. So if some other than you uses same VCX, primary-key can't be generated without knowing parameters you have used.

AT

P.S.

I'v also tought to offer this like a new project in VFPX (SednaX) to make it
rock solid ( = no bugs :)) ) VFP FFC. It depends also that VFPX admins approve this AND also that there are enough people to join to develope it.