>>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.

Where is such a purpose (if such a thing existed or "vfp content") stated in the EULA in a legally binding way?

>Microsoft had intended VFP to be a desktop app run on Windows only, meaning you have circumvented its technical limitations.

the ability to create activeX components was often cited - also running those activeX middleware on web servers - by MS and their publications.

>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.

true, but where does FIC go against these rules ?

>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.

they either hit a runtime running on windoze or something generated out of metadata not hitting fox runtimes - where is the problem?
MS is often critised for FUD. FUD from other sources is not better.