Re: Copyright of data

Don wrote:

> Bob, et al,
>
> > Putting code "in escrow" isn't to protect the vendor, but to
> > protect the customer in case the vendor goes "belly up".
> >
>
> The problem with this is that if a company goes toes up, the software in
> escrow is a asset that can be attached by the creditors.  This means it
> can be tied up in court for a helluva longer time than you can wait.  I
> NEVER NEVER NEVER allow ANY client to agree to a software firm that
> insists on this arrangement, soley for this reason.  I always insist that
> a client require the source code delivery to be part of the software
> contract.  If a vendor has a problem with delivering source code, then I
> dont' need the vendor...there's alot of software houses out there...
>
> ...just my opinion...and I might be wrong...:)
>
> Don in DC metro

I agree.  Our company policy has always been to deliver source.  After all, our
office could get struck by lightning and we would all be fried!  The corporation
continues to live, hopefully, and the client then, as always, gets to choose 
it's
support organization.

Even in such a case the client is still restricted from distribution, in whole 
or
part, original or modified, and the corporation just needs to have plans in 
place
for the shareholders protection in the event of a violation.  But just because 1
in X may TRY to violate does not mean that the remaining need be inconvenienced.

Sort of like most of your laws should be. :)

IMHO the software houses that are unwilling to deliver source are trying to
create a "captive" audience for modification/support services.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---