Good list of issues - I'll revise my boilerplates this weekend!

>>My job wants to know how I make my EXEs to interface with the users.
>>After I teach them this, they will not need me anymore...
>>Is there a way I can get around this? I must give them the source code.
>
>Robert,
>
>I agree with Jim Booth on this. Most software is too complex anyway and if the client wants to rip me off they're going to either have to a) find a dishonest FoxPro developer or b) train one and that will cost a lot more I'd expect than just paying me to come back. What most folks fail to realize is that no matter how you approach it a 'solution' is going to basically cost the same. Outside help at more $ per hour but shorter hours or inside help at less $$ per hour but for longer hours.
>
>40 hours at 100 = 4000
>
>-or-
>
>200 hours at 20 = 4000
>
>There are four additional issues I'd cover:
>
>1) A non-compete - That is, the client is barred from using the source code to compete with me.
>
>2) A notice that while I reserve my ownership rights to the source code that the client has a perpetual non-exclusive right to modify the source for their internal use.
>
>3) All 3rd party software's source code will NOT be provided. Progrrams like Stonefield's Data product, Visual MaxFrame, etc.
>
>4) There is an interesting federal law that excludes federal agencies specifically from copyright law. So, if you provide them with one copy they can make as many as they wish without paying you for it. Many people have lost their shirts because the feds have ripped them off. However, you can get around this and FoxFire software has an example of the words you need to insert in all your source code that, like a magic wand, allows you to now prohibit your software from being freely passed around. It's a 'back door' and you need to make sure you protect yourself. Contact Bill Wood at Micromega and I'd bet he would be more than happy to provide you with an example.