>>>I personally never had the need for it, but yes I agree. But really it is about the EULA and whether it is reasonable.
>
>I knew when I bought it that you're only supposed to use it for yourself. Whether this is enforceable isn't a concern to me: it's what I agreed, and in his shoes I'm sure I'd want the same.

Many EULAs can only be read when you already bought the product. What do you do when you disagree and it is not refundable ?

>>>Your neighbour does not hold any license to MS office, but knocks on your door to create, modify or print a word document (on your computer). Is it resonable to have an EULA that says that the software can only be used by the owner of the software and only for documents he owns? Please raise your finger who will deny your friendly neighbour to do this.
>
>Seems to me there are many business models and we could both spend all day coming up with examples. ;-) E.g. see what happens if you start sharing MS's CRM software with more than one company for a fee, or if you wanted to use VFP on Wine/Linux.

Which are legitimate scenarios and questions.

>>>Disclaimer. I do not own refox, never used it as I have backups and sourcecontrol in place. I have all respect for JanB in creating and maintaining REFOX and hope he will continue to be profitable However I would argue that if his business is depended on this particular T/C, then I think the product has no viable commercial future.
>
>I hope there's enough $ for him to keep going. FWIW, Refox saved my bacon some years back when a crash took out a session of tricky work that would have been a bear to replicate, and had not yet been backed up or source controlled. How often do you back up?

Every change to our source code is checked in (through source control stored in a data centre) when completed and in practise that is several times a day. We have a team of developers working from different locations in the world working through source control. The source control database is backed up and stored off site every day. Even if both are lost the developers will have a recent state of the source code since they got the latest version (which they do daily). So in our case this risk is covered quite solid.

Walter,