D
DanK
You have to cripple it!
1) Limit the files to say 100 records.
2) Prevent the actual printing of any report. Make the
command Print Preview so they can see ON THE SCREEN what
they COULD print out wiht the full version.
3) Set a time bomb. If date() = 1/1/2004 then delete
tables, files; really destroy the database. Let them know
ahead of time that it's going to die.
4) Create a crippled version that they can activate with a
phone call. For example, they pay you and get a phone
number to call. You tell them where in the code to go and
activate it. For example, when the database opens up it
sets a global variable X to say 100. Then, you add code
all over the place that checks the value of X. If it's
100, then they can't print, they can only print preview.
There's code that checks for the date 1/1/04 and if X =
100, self destruct. But when they call, you tell them
where to go to remove or modify the code that sets X to
100.
1) Limit the files to say 100 records.
2) Prevent the actual printing of any report. Make the
command Print Preview so they can see ON THE SCREEN what
they COULD print out wiht the full version.
3) Set a time bomb. If date() = 1/1/2004 then delete
tables, files; really destroy the database. Let them know
ahead of time that it's going to die.
4) Create a crippled version that they can activate with a
phone call. For example, they pay you and get a phone
number to call. You tell them where in the code to go and
activate it. For example, when the database opens up it
sets a global variable X to say 100. Then, you add code
all over the place that checks the value of X. If it's
100, then they can't print, they can only print preview.
There's code that checks for the date 1/1/04 and if X =
100, self destruct. But when they call, you tell them
where to go to remove or modify the code that sets X to
100.