>In those situations that require it (mostly apps on the web), the frontend will be .NET. If any significant data munging is required, VFP will probably handle it and send the application an XML string.
>
>Naturally, for those applications that still fall into the two tier C/S, VFP will probably be, in most cases, the front end and data engine.

George, you just described my current strategy. I think ASP.NET and VFP are a perfect fit. VFP's ability to process data and strings quickly makes it a great (dare I say perfect) choice especially when XML is involved.