>Let me count the ways... To put it succinctly, the only reason for not doing it in VFP is if I was interested in doing it "the microsoft way" which I am wholeheartedly against. There's little to no technical reason to not do it in VFP.

I know nothing of the application in question so I'm curious to know which aspect of web site development you think would be well served by VFP?
The Data engine? HTML page construction? SOAP/Web services? Something else?

>There's zero reason to move away from VFP from a financial perspective unless you have the mis-fortune of having to market
Microsoft's latest and greatest to your clients.

You think it is easier to market an unsupported 32-bit single-threaded solution that was never remotely intended for a web hosted environment?

> It's easier to do it in VFP. It's just plain more fun to do it in VFP.

Have you already done it in VFP? I have. Once. Fun is not the word that springs to mind.
Have you done any web site development using anything else?

> I can develop web applications like they do in PHP. I don't feel like I'm locked in to M$ dog poop. You name it!

I'm happy to argue choice of tool based on technical merits. If you want to use some other criteria such as the moral stance and business practices of the provider then I'm afraid I'm not interested....

>>Yes
>
>>You mean why would I choose not to rewrite most of my vfp code? Seriously?
>>
>>>You're right in that this is probably a moot point.
>>>Your ability to power a web site using VFP is unlikely to be seen by MS as posing a serious threat to their revenue stream. But if you are not just >doing it to p*ss off MS then may I ask why you would choose to do so?