>>I have live .NET apps that run full data app requests at several thousand req/sec on a single dual core box and it's barely pushing the server. That's simply not possible with FoxPro. You can make that work too - but it requires a lot more horsepower and scaling out to multiple boxes.
>
>Agreed
>
>Given the declining cost of hardware and the markets where VFP/WC/FoxInCloud operate -- SMB below 1k users -- it's a viable (and proven) solution to run such business apps on the Web.
>
>eg. the app I mentioned earlier works for a 300 users company; H/W + S/W cost is a couple of $ per user per month, negligible compared to wages.

Yes - and that is where the value for FoxPro tools is mainly IMHO - in supporting or extending existing applications. I'm not so sure for new development since other solutions offer better performance and maintainability.

Keep in mind that the costs you are quoting are probably based on your expertise (which is above the norm by a lot) and existing experience having built solutions using your tools (and mine). For you and me setting up and maintaining a new application is a piece of cake, but for new developers getting started there's a learning curve and a gap of basic understanding of the concepts required (COM, COM Interop, IIS Config, etc. etc.). It's not as easy to slap a Web Connection application onto a server. I've tried to make this a lot easier in 6.0 with the new default project templates and scripting but even so you need to know what's what in order to fix if there is a problem.

I'm afraid, these days many tools sell based on administrative costs, learning curves and cost to run an application above all.

+++ Rick ---