>Humm... the protective side of me would agree, however, I know that if they opened up the project, then went to a screen and opened that, if they start getting errors that class/object not found, they could get upset. Their desire for the source code and definition of what they felt they are paying for meant that they would be able to take it further, with other developers... if they needed to.
>
>They also wanted a "warranty of work" for one year (couldn't get out of that one). I do have a clause that states, if anyone messes with the code, in any way shape or form during that year, the warranty is void though. ;)
>
>
>
>>
>>Thank you. I just got through with having to spell out things for a potential client, so it was pretty fresh <g>
>>
>>Brian, I also meant to mention the point that Rick made. Document the specifics of what is yours and what is theirs, file by file. This is one place where OO really comes in handy, since you can separate your functions from the custom functions in different class libraries.