>I tend to agree with everything you said and yes, I do reserve rights to specific class and program libraries that I carry from job to job and I reserve the right to add 'generic' code to that library even during a job. On the other hand, code specific for the client that can only be used in their specific job in their specific industry I am more willing to part with, like the way they calculate the amount of yarn that goes into a T-shirt based on style and size.
>
>But the point I had hoped to make is that I don't guarentee the code if the client has access to the source, can make changes, and cause errors that I am then required to track down because they claim they didn't touch anything. But of course, get everything in writing and you really need to keep ownership of any generic code. After the acceptance period for the project, I might then give then 'license' to all the code, but rarely if ever before.
>
>Mike

That's a good policy. I recently licensed my framework to a person that is rewriting a Fox2x application to VFP 6.0. This is a vertical market application. I put several provisions in the contract about use of the framework that prohibits him from using it for anything else and protects me should he sell the product rights. One thing I did, for example, is require that he show my copyright notice to "portions" of the application.