[AccessD] Source Code Escrow

I'm not familiar with the concept but it seems to me that you would have
to keep updating and patching the code deposited in escrow or you would
fail in the intent of the thing.  What format would that "code" be and
how would it be stored?  I suppose that if you deposited a CD containing
the native application you could keep giving them updated CDs, but who
would be responsible for keeping track of which was which and how many
generations would they hold?

Charlotte Foust


-----Original Message-----
From: Griffiths, Richard [mailto:R.Griffiths at bury.gov.uk] 
Sent: Thursday, September 15, 2005 5:59 AM
To: AccessD
Subject: [AccessD] Source Code Escrow


Hi Group

I have been asked about Source Code Escrow regarding a system I have
written.  My understanding is that I deposit the source with a third
party 
and should my business fail or it fails to deliver support etc for the
product the licensee can apply to have access/a copy of the source code
to allow support/further development.

Any one any experience here, pitfalls etc. Another question is what sort
of fee (subscription) to charge the licensee - is there a rule of thumb,
standard fees etc

Cheers

Richard
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com