Craig,

The general consensus is that we should have the user call us for
a product registration number to be used to be used for installation
purposes. If user goes to a new machine, they simply contact us for
a new product number. I don't like this idea, but I don't know
of a better way.

>>If you are selling software, you do not want the user to be
>>able to use it more than one time.
>>
>>
>>
>>>>vfp 3.0 win 95
>>>>
>>>>Hello all,
>>>>
>>>>What is the best way to write protect software so that
>>>>it can only be installed once via diskette? via cd-rom?
>>>>
>>>>Is there a way to accomplish this via the setup wizard?
>>>>
>>>>Thanks and have a good day!
>>>>
>>>>Becky
>>>
>>>
>>>The setup wizard does not have this capability. Why would you want to limit this?
>
>
>Hmmm....I can see some problems with this. While I agree with the idea that you need to purchase one copy for each user, what happens if a particular user gets a new PC? Do they need to buy another copy of your application...even though that user was already using your application? The registry on my NT box recently became corrupted, forcing me to reload everything. I would have been extremely upset if I would have to buy another copy of any application to reinstall it.
>
>If you want to limit installing on another PC, you should incorporate a dongle. THis is a hardware gizmo that plugs into the parallel port. Without the dongle, the application doesn't run. However, my experience has shown that they are more trouble than they are worth.
>
>You might be better off limiting the number of simultaneous users. I am working on a web page that will describe an easy way to do this. It will be on my web site no later than Monday. Check at www.xmission.com/~craigb.