I am making a program on a contract, this
is my first paid work.
I will only be paid when the client is satisfied
with my work.
Im a bit concerned that since our only contact is
via the Internet that when I send them the
software to evaluate, they will just take it and not pay.
So can anyone tell me what is the standard
or preffered way to make a trial version
of software that will not function past the
expiry date of the trial period?

Thanks for any help!

Phill.

Hi Phill,

I do not think there is any standards with regards to a TRIAL version.
There are several things you can do depending on what your program is supposed to do.
If it is document oriented, remove the 'Save' from the program so people can see it works, but not actually use it until they pay.
If it is database oriented, put a limit on the number of records the program can deal with.
If it is, etc, etc, etc.

Hope this help.



Phill wrote:

> I am making a program on a contract, this
> is my first paid work.
> I will only be paid when the client is satisfied
> with my work.
> Im a bit concerned that since our only contact is
> via the Internet that when I send them the
> software to evaluate, they will just take it and not pay.
> So can anyone tell me what is the standard
> or preffered way to make a trial version
> of software that will not function past the
> expiry date of the trial period?
> 
> Thanks for any help!
> 
> Phill.
> 
> 
> 

-- 
ManiaC++
Jan Knepper

Do you mean and then send them
another version once they have paid?

I mean after I have sent them the trial
version, once they have paid I can
send them a serial number or somthing
which they enter and the full version functions.
What could be the proceedure once the
serial number is entered?
Should my program write it to a property file,
or the registry, so that the program can read it at a later date to test
whether it should start as a trial or full version?

I hope I am clear.
Thanks for your help!


"Jan Knepper" <jan@smartsoft.us> wrote in message news:bp3ur4$mo2$1@digitaldaemon.com...
> Hi Phill,
>
> I do not think there is any standards with regards to a TRIAL version.
> There are several things you can do depending on what your program is
> supposed to do.
> If it is document oriented, remove the 'Save' from the program so people
> can see it works, but not actually use it until they pay.
> If it is database oriented, put a limit on the number of records the
> program can deal with.
> If it is, etc, etc, etc.
>
> Hope this help.
>
>
>
> Phill wrote:
>
> > I am making a program on a contract, this
> > is my first paid work.
> > I will only be paid when the client is satisfied
> > with my work.
> > Im a bit concerned that since our only contact is
> > via the Internet that when I send them the
> > software to evaluate, they will just take it and not pay.
> > So can anyone tell me what is the standard
> > or preffered way to make a trial version
> > of software that will not function past the
> > expiry date of the trial period?
> >
> > Thanks for any help!
> >
> > Phill.
> >
> >
> >
>
> --
> ManiaC++
> Jan Knepper
>

How can i create a 30 days trial version in Visual C++(MFC) or like a winzip trial version please any one help me to solve out this problem.


thanks in advance
keshav

In article <bp3vmq$ocg$1@digitaldaemon.com>, Phill says...
>
>Do you mean and then send them
>another version once they have paid?
>
>I mean after I have sent them the trial
>version, once they have paid I can
>send them a serial number or somthing
>which they enter and the full version functions.
>What could be the proceedure once the
>serial number is entered?
>Should my program write it to a property file,
>or the registry, so that the program can read it at a later date to test
>whether it should start as a trial or full version?
>
>I hope I am clear.
>Thanks for your help!
>
>
>"Jan Knepper" <jan@smartsoft.us> wrote in message news:bp3ur4$mo2$1@digitaldaemon.com...
>> Hi Phill,
>>
>> I do not think there is any standards with regards to a TRIAL version.
>> There are several things you can do depending on what your program is
>> supposed to do.
>> If it is document oriented, remove the 'Save' from the program so people
>> can see it works, but not actually use it until they pay.
>> If it is database oriented, put a limit on the number of records the
>> program can deal with.
>> If it is, etc, etc, etc.
>>
>> Hope this help.
>>
>>
>>
>> Phill wrote:
>>
>> > I am making a program on a contract, this
>> > is my first paid work.
>> > I will only be paid when the client is satisfied
>> > with my work.
>> > Im a bit concerned that since our only contact is
>> > via the Internet that when I send them the
>> > software to evaluate, they will just take it and not pay.
>> > So can anyone tell me what is the standard
>> > or preffered way to make a trial version
>> > of software that will not function past the
>> > expiry date of the trial period?
>> >
>> > Thanks for any help!
>> >
>> > Phill.
>> >
>> >
>> >
>>
>> --
>> ManiaC++
>> Jan Knepper
>>
>
>

During installation, or when the program run for the first time, use say the date, time, volume number, maching tag, hard disk space etc to generate a number and stored it in the registry. This becomes the "activation code". When customer pays, they neet to submit the number to you. You use the number as input to you secret algorithm to generate an unlock key. The rest is up to your imigination.

Naturally no software copy protection scheme is secure... That's why hardware dongles are made...

I use the Silabs' USB 8051 microcontroller to store a piece of code in our hardware. You can find those micros at www.silabs.com



<keshu82_sh@hotmail.com> wrote in message news:dh85kj$iti$1@digitaldaemon.com...
> How can i create a 30 days trial version in Visual C++(MFC) or like a
winzip
> trial version please any one help me to solve out this problem.
>
>
> thanks in advance
> keshav