It depends on the client, but an escrow clause in the contract (allowing for client-access to the code if we go bust, or decide to discontinue the product) helps us provide the 'comfort' factor, with riders for third-party libraries that we may be using. See http://www.ncc.co.uk/ (although there are plenty of others).


>Just out of curiousity, those of you who are independant contractors and developers; how much of your source code do you normally give over to clients? Most people (prospective clients) I've talked to want rights to the code, which is understandable. But how do you protect your class libraries and other custom methods? If they "own" the source code as "work for hire", custom class libraries need to be turned over in addition to forms and .prg's, right? Otherwise they can't modify the application in the future.
>
>If a client hires you to develop an app, and then gets someone else to help out or build a different part, what's to keep the other developer from copying your stuff? Or is that just a part of the business?
>
>
>- Brian