>Actually I've found PHP (and Apache) quite easy to get running and get usable results. True, I spent about three full days (spread across two weeks) getting Apache running my pages, but then I had just as much, if not more, frustration in trying to get a VFP COM server run again under IIS 5, even with Rick's wizards. At least with PHP when I screw up, the error messages are right on the spot, not cryptic, and it's quite easy to find and fix.

Well part of the reason for that is that COM configuration is inherently difficult, but if you want to use VFP for Web applications with IIS COM is pretty much the only high performance option out there... I won't deny that that approach has its issues, although there have been changes made in Web Connection recently that should mitigate most of this (I'm talknig about the DCOM permissions issues here specifically).

The problem on that end specifically is using VFP on the Web because VFP was never natively designed to run as a Web backend so any way you look at it hooking VFP into a Web application is working around the limitations around VFP's architecture.

These issues don't exist either with PHP or ASP.NET for that matter. But of course then you lose the ability to use VFP... Scripting languages are by definition to be easy to use once you've set up the server. Server configuration is rarely easy though and even the best efforts at auto-configuration can be foiled by overzealous Administrative policies <s>...

Trade offs are everywhere <s>...