Thanks,
Matthew

Regards Asbjoern.
Asbjoern Aamot [Microsoft.MVP-VB]
P.b. 562 N-6901 Floroe , NORWAY
http://www.vestdata.no/~asea/asbj.htm See also http://www.mvps.org

WARNING: I do normally not answer VB-related Q recieved by email !
So IF You wish for an answer, PLS send Q to microsoft.public.vb.(related
topic)
========================================
My opinions do not necessarily represent
the expression of official Microsoft policy.
I volunteer my time through the MVP program.
I am not employed by Microsoft.
========================================

Make a splash-screen to Your app.
-crypt Your name, emailadress, and contact info into the code,
decrypt and show on formload,
-Make a control-sub to check that Your name/email are valid, if not stop
running,
-make a lisence validate-code, use registry or ini to save user/companyname,
and licensecode,
-also show username/company if correct licensecode is valid, else  show
DEMO,
limit functions as save, and similar importance, but let an unregistered
copy
give a demo, SHOW info on splash-screen

-You might use "NAME 3 Licenses" as username, so user have the right to
have more than one copy of Your app, (still need only 1 (one) setupdisk-set)
-Include Your name and contactinfo to helpfiles, and so on,
-give info of NO SUPPORT to unregistered versions/demoes
-If user/companyname OR licensecode are tampered with, AUTOMATICALLY
Change registration to DEMOVERSION, with No save, and other restrictions
(and update INI / registry with DEMOinfo)

The limited demo-version You might also send to possible buyers, so they may
take
a preview of Your app, and IF they wish to use it then they have to register
to get
SAVE and other limited things to work . You now only have to issue a
license-code
to the user. (and of course; have a registration-form (frm) in Your
app...;-)

-Do NOT use hardware-locks, or system-spesific info, such as disk-serial,
type of videocard,or other info that might change if the user upgrades
hi's/her's equipment,
This will only create extra work for You, and more trouble for the user.

You MUST expect that someone would try to tamper with Your app, and try to
make illegal copies.
Count on it. Whatever kind of copyprotection soft/hardware you use.
But : What if 10 users uses Your app WITHOUT a proper License ?
And You have 100's or 1000's of legal users ?
The 10 illegal users would NOT have the right for support, neither right for
upgrades,
and so on. "They shouldn't bother You."
More complex security as hardwareinfo/ locks, etc would cost You morefor
support,
than the lack of earning from the few pirates.

Also as an extra tip:
Put one copy of the setupdisk(s) in a sealed envelope, snail-mail to
Yourself,
put into a bank-deposit-box, and now You have dated proof that the app is
Yours.
In case of a trial or something, DO NOT OPEN the envelope Yourself, but let
Police,
a lawyer or similar open it. Get vitness for the opening...

This is how I do it, and it works pretty well for me.
I guess there might be some illegal copies out there, but I do not bother
about it.

Regards, Asbjoern.