>>snip<<
>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
Totally agree. Anything specific for that client they can have to use as they wish.
I would always include in the contract a declaration regarding responsibilities (when? *g*) the client changes the code and, of course, some sort of benchmark to establish a a "baseline" of some sort.
Best,
Best,
DD
A man is no fool who gives up that which he cannot keep for that which he cannot lose.
Everything I don't understand must be easy!
The difficulty of any task is measured by the capacity of the agent performing the work.
