Rick,
IMHO, as soon as Microsoft announced that they would stop supporting VFP, the EULA became irrelavant. I have an application that I sold to many customers. If and when I go out of business, I fully expect the customers to decompile or do whatever they want with my application.
Even resell it to other companies.

>>FoxInCloud is a VFP + JS software layer that enables VFP applications to run the same code on a desktop or a web server with a browser-based GUI (using HTML+CSS+JS+AJAX)
>>
>>It's up to the software vendor using FoxInCloud to comply with this clause of EULA.
>
>True. True. You also have an equal responsibility to honor and comply with the terms of the EULA.
>
>For example, your product takes VFP content and puts it on the web, a feature Microsoft purposefully left out of VFP. Microsoft had intended VFP to be a desktop app run on Windows only, meaning you have circumvented its technical limitations. Per Microsoft's design and license, the people who use VFP runtimes would have to be running Windows, part of Microsoft's goals for a closed ecosystem, and additional revenue as even today it is illegal to run VFP runtime apps on Linux or Macs, unless you run the full developer install.
>
>Your product takes that a step further.
>
>Not only do FoxInCloud users not have to have VFP developer or the VFP runtimes installed, or even be running Windows, but the running version of VFP is on a server, being used by whoever hits the site, as a commercial service by you, and by FoxInCloud users.
>
>
>>> * use it for commercial software hosting services.
>>
>>>These last portions, "rent, lease or lend it" and "use it for commercial software hosting services" ... is this what FoxInCloud does by leveraging VFP onto the web -- meaning anyone can access it (in that way)?
>>>Or does FoxInCloud simply use the source code and do its own thing in complete isolation of any VFP-code-based services?