So the real basis for this thread is a statement said long ago here... ".NET sucks when it comes to handling data VFP is much better".

Pity, really. I thought we were well beyond that. Apparently, some of us aren't and wait patiently to extract some form of 'revenge'.

I thought initially you would be wasting your time. Now I see you'll be wasting my time!

Let it go, Rod.




>I want to address one more comment<g>
>
>>>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"
>
>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....
>
>ROdman