Wes Reed wrote: <snip> We generally contract with our clients to license any programming to them with the rights to do anything they want with it forever but retain ownership. To us, this makes perfect sense. </snip> me too. <snip> How common is this sort of licensing practice? We know people who do the same but I am wondering if we are just a small minority. If you do this, do you have suggestions about how to make this palatable to the client? </snip> i do this it wherever i can - usually by asking my line manager's permission. as a contractor, copyright always subsists with the client and i have to get exceptions. if i'm clear and explain that no proprietary knowledge or data will ever leave the building, just plain vanilla routines and procedures, they are usually amenable, providing i don't take it down the road and use it for a competitor ;-) <snip> Do you know of any references that would explain/describe this kind of agreement? </snip> sorry no - if you find any, please let me know it would be very useful to have a standard contract clause. david -- If you are not the intended recipient of this e-mail, please preserve the confidentiality of it and advise the sender immediately of any error in transmission. Any disclosure, copying, distribution or action taken, or omitted to be taken, by an unauthorised recipient in reliance upon the contents of this e-mail is prohibited. Somerfield cannot accept liability for any damage which you may sustain as a result of software viruses so please carry out your own virus checks before opening an attachment. In replying to this e-mail you are granting the right for that reply to be forwarded to any other individual within the business and also to be read by others. Any views expressed by an individual within this message do not necessarily reflect the views of Somerfield. Somerfield reserves the right to intercept, monitor and record communications for lawful business purposes.