>>Let's go back to the basic case we started with. We have the XYZ desktop app which our company uses and/or sells. This app was develeoped over years using VFP and commonly used VFP tools.
>>
>>Now uh ih, we need our desktop app to be able to be run "on the web." Wwe estavblish that there is a reason to do so
>>
>>Next we evaluate RemoteApp por similar, which takes care of most scenarios. I gave a session on TS at SW Fox and when I asked for questions, I always got the same one -- why would any build a "web app" when TS is available?
>>
>Mobility.
>A browser-based app can run on anything that can access the web with no setup required.

Yep, that is the reason.

>
>
>>But let's assume we now find a dollars and cents business case for not using TS and creating a browser based "web app." But perhaps some users do want a desktop app. Wow, we say, it doesn't seem like VFP can do that for us, so we think we will have to spend a bunch of money and move our app from VFP to platform X.
>>
>>Then we realize that the entire web is based on HTML/JS/CSS, and that combo could never become obsolete easily. So we grab FoxInCloud and discover we can keep our desktop app and also have all our app's forms, classes, etc. run automatically as HTML/JS/CSS. Minimal conversion effort required. As long as we are actually dealing with VFP and not old FPW type do//say prg's, we are set.
>>
>>Hard to come up with a scenario where that would not work and we would have to actually mnove to a different platform.
>
>Agree.
>
>But, let's consider another scenario.
>The desktop apps are still needed but the business requires some completely new functions that are mobile.
>They'll share SQL Server data with the desktop apps but all the functions are new.
>You happen to know some hotshot PHP programmers who take a look at the spec and give you a really good bid.
>What is wrong with considering that approach?

I actually like PHP, but:

1. The PHP app will be more expensive to develop.
2. Maintaining rtwo codes bases, web and desktop,when could have 1 code base for both
3. Can use , besides JS, any language supported by HTML/Web server directly from VFP while still keeping one code base.
4. Can sync appearances as much or as little as desired between web and desktop
5. Superior data handling via VFP