General information
Title:
How to protect your VFP code ?
I intend to offer VFP5 made software available from an internet server as a resource (shareware) instead of moving CDs and diskettes around.
The questions are :
1 - How can i protect my code from decompilation,
2 - How can i organise a SIMPLE protection scheme equivalent to the
ones found in most sharewares:
a - message box informing that a payment should be made,
b - the user gets a key number (upon payment of a fee),
c - user updates the software via a specific procedure
that "brands" the software... i am obviously not looking
a costly total protection but a one solid enough to prompt
for a limited payment.
I understand that solution to question 1 is REFOX, point. Concerning this software i'd like to hear from those would use it whether it has any side effect on application usage on installation process ?
Concerning question 2, i should really like to hear from you all about getting people to pay for software and, a hot subject, internet-based software distribution?
Regards to all UT members
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only