>This statement in no way refutes what I said about architecture. This is more akin to echoing marketing rhetoric. If you take web services out of the mix, your premise falls apart.

I don't plan on taking Web servuces out if the mix. I don't think that they are small a piece as you think they are.

>As far as what tool a developer is comfortable with, I think you are going to find that developers will get comfortable with VS .NET very fast.

There is alot to get comfortable with. XML, the .NET framework, ASP.NET, ADO.NET, and SQL Server being involved in the typical .NET solution. No doubt, many developers will use VS.NET, I am not debating its usefullness or abilites, but for many VFP developers, VFP does exactly what it needs to do very comfortably and effortlessly.

>That said, businesses don't pick tools based on what developers are comfortable with. They pick the tools they feel will be innovated and supported.

You definitaly are making some huge generalizations here. Many of my clients woudl rather do their job (which is never computer related) than worry about using the most innovated technologies in the solutions we develop for them. Bottom line, we can get done what they want done using Visual FoxPro, and we can offer them the exact same next generation applications using the same Web service technologies and standards that VS.NET does.