>> In this Perspective I will immediately roll out the possibility of developing in VFP since I read an article saying that VFP is geared toward client-server applications and not distributed, web applications. <<

I agree this is one part of the article that could be modified. The fact is, Microsoft considers Visual FoxPro a great development tool for creating "rich client" database applicaitions, primarly client-server (1, 2, or n tier). VFP is also a fantastic client to SQL Server 2000. Because VFP 7.0 fully supports XML Web services, VFP7 makes a great rich client for Windows in creating distributed applications (part of the .NET strategy).

Client server is not dead, just like COM is not dead. When people say something is dead, what they should saying really is that the technology is not evolving, it may just remain as is, but that might last for 5+ years. Just like COM, ADO objects, and client server applications, they will all be fully useful and valid over the next 5+ years. This while new technology like VS .NET is migrating and evolving towards distributed computing. Even in distributed computing, client server still exists, it is just more disconnected and over HTTP instead of on a LAN/WAN.

I really don't think the general person that reads Jenny Brown's article in FPA Mag will have any negative comments about it, nor will they read anything invalid. I think you are spending too much time analyzing the comment about the future of client server, and the way you read it was not the intent in the article.