>I want to address one more comment<g>

Sure :)


>
>>>A more fruitful debate, imho, would be to simply, honestly, and openly >>list the top pro's and con's of each tool, and to list appropiate target >>applications and end-users for each development tool. Perhaps even expand >>beyond the VFP/.Net duality and include other powerful development tools >>like Delphi, Java, PHP, Python. Why not have developers post their >>success stories about their best applications? Why were they successful? >>Why was the tool chosen? This would be much more useful imo
>
>This is all subjective. The basic premise that we are disussing is this...
>
>".NET sucks when it comes to handling data VFP is much better"

I was not discussing nor advocating that statement as it was not offered in this new thread that you created. I am addressing only points started in this new thread as per the thread subject.


>This is an opinion of some folks here. I want to take an objective look at how each platform handles data. There are a number of mechanisms for handling data in each platform. How do they work? I am not looking to sell .NET people in this discussion will take a look at the mechanisms for dealing with data in each platform and judge for themselves.
>
>For instance one item to discuss is the concept of DATA SESSIONS.
>
>FoxPro's method of managing data in an isolated manner is the concept of a DATA SESSION. You can open and maniulate the contents of table(s) in an individual data session.
>
>.NET's method of managing data in an isolated manner is to encapsulate all data into an object known as a dataset. You can open and manipulate the contents of table(s) into multiple datasets.
>
>This is the type of info I am talking about....

Go for it because then we are discussing how each dev tool handles data and *not* comparing dev tools per se. Therefore we do not need to remove anything from either dev tool but rather focus on how data is manipulated in one vs another.

Personally I believe most all major dev tools have strengths and weaknesses. Beyond broad brush stroke comparisons and obvious core functionalities I think comparisons quickly become pointless. Furthermore, I think individual developer skills (or lack thereof) more often than not will erase actual or perceived benefits of one dev tool over another :)