What are your thoughts (anyone) about writing a sort of "self-destruct"
mechanism.  Clearly state in your agreements that the finished product
will be placed on the client's server.  However, if payment is not
received in full, then the script will automatically delete itself after
so many days, or something similar.  If payment is received, then you
will send a "patch" to the program to remove the mechanism.  This would
then stop the client from changing passwords on the server, and stopping
you from being able to take it back down.

Ivan - is this even legal?  I know you can't give 'official' advice, but
is this even a possibility?

Jeremy Brown



-----Original Message-----
From: owner-hwg-business(at)hwg.org [mailto:owner-hwg-business(at)hwg.org] On
Behalf Of Ivan Hoffman
Sent: Monday, June 24, 2002 1:03 PM
To: David Jourard; hwg-business(at)hwg.org
Subject: Re: How to get a client to pay

At 12:55 PM 6/24/2002 -0500, David Jourard wrote:
>Hi,
>
>I've just completed a large CGI application using Perl.  I took 50%
when I 
>started but now that it is complete and installed on their server


You should not be posting anything onto a client's server until you are 
fully paid.  But this issue, and many others, must be covered in a 
thoroughly drafted agreement.

This reply is not legal advice and does not create any attorney client 
relationship.




IVAN HOFFMAN, B.A., J.D.
Attorney at Law
Lawyering With Integrity
Internet Law, Publishing Law, Copyrights, Trademarks, Corporate Training

and Online Education Law, Web Design Law, Music Law.  *A 6 Times Award 
Winning Site.* http://www.ivanhoffman.com

HTML: hwg-business mailing list archives, maintained by Webmasters @ IWA