Ken at any type I say that Jenny Brown says that client-server is dead see the end of quotes The next statement is from my responsibility.
To prove this How many companies now develop new client-server applications?
Take for example SAP SAP ERP was a typical example of client-server applications does the new version still is, don't think so.
would be interesting to now how may of VFP developers is doing typical client-server applications.
What Jenny Brown says in his article is that while .NET is for distributed, web-based applications VFP is geared to client-server applications.
This is the statement that I totally disagree and that I point out as being a shoot in the foot of VFP.
Lets analysis this for example I'm a non technical or even a technical Program Manager and I'm analyzing how the new software for my company should be development first thing that I know is that all the software should be development as n-tier so that I can have various mode of accessing to it I want to be able to access it via a Windows front end, I also want a Web front end and a WAP front end for now. 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.

This is what I wanted to point it out and as I said at the end of my post in any manner I was trying to be unrespetfull to Jenny Brown.

>>While .NET is geared primarily for distributed, Web-based applications, VFP will continue to be geared toward robust client-server applications." since everybody now is saying that client-server is dead and in my experience this is true now all the applications are being developed as n-tier applications, then all new developers shouldn't use VFP unless they are designing desktop applications and don't have any plans that those applications should run in a n-tier environment.
>>Then also if this is true then why the heck does Microsoft put all this new features in VFP if we are to development old types of client-server application or desktop applications then Why do we need to create web services and why do we need XML?
>
>I read this article by Jenny Brown in FoxPro Advisor magazine, and I have to say I completely disagree with your summary and comments about what what written. To start, Jenny is a VFP developer, one who has taken the time to also develop in VS .NET beta 2, so she has the proper perspective in commenting on VFP and .NET.
>
>Nowhere in the article does it say client-server applications are dead, and nowhere in the article does it imply that VFP doesn't fit will in .NET.
>XML Web services is about creating distributed applications, and VFP 7.0 allows developers to venture into this new technology while still supporting all the great 1 to n tier development strategies as before.
>
>I suggest you review the comments that Steve Ballmer recently made about VFP 7.0 and how it relates to .NET at http://msdn.microsoft.com/vfoxpro/prodinfo/ballmer.asp
>
>Everyone who reads Jenny's article in FoxPro Advisor magazine should take it seriously and consider it an extremely well written article, and it states the right information about VFP and .NET. Just take a look at the summary sentence in the article:
>
>"What's important to realize is that even though Visual FoxPro isn't part of Visual Studio.NET, it can still play an important role in a .NET solution—that is, if you choose to incorporate it into a .NET solution."
>
>The above statement is completely accurate and is an excellent summary. Those interested in using VFP7 along with VS .NET should consider upgrading to the new MSDN Professional subscription level that includes VFP7, VS .NET, VS6, and all the Windows operating systems and SDKs. A good complement to this FoxPro Advisor article on VFP and .NET is the Web Services whitepaper for VFP at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fox7help/html/fogrfWebServicesInVisualFoxPro.asp