Yes, he is looking at it from a VFP perspective. That's to be expected, of course. We have to look at the reality of a situation and not how it could/should be (except for efforts to submit suggestions and encourage new and better features). However, is your post saying "just get over that ease of use stuff and accept less?" Is it like telling the iPhone user (before the more capable competitors arrived) to just change their perspective and accept the inferior interface of a different cell phone? Granted, you might respond by saying there are more sophisticated data-handling capabilites in .NET in some ways, yet where is the ease of use? We've done sophisticated data-handling in VFP for quite some time and have not had to struggle to the extent you do in .NET. Wouldn't you say that VFP developers all go through this and feel like they've stepped back in time - they feel like their data handling capabilities have been hobbled? Isn't it frustrating when you know how it can be and others in the industry - those who've never used VFP - just seem to accept it and never expect more?

>You're looking at data handling from a very VFP perspective. You have to remember that almost all other languages don't have ANY native data manipulation capabilities but instead do much of their data munging on the back-end server. You need to think differently and keep that in mind. Go back to VFP and look at how you work with ADO, then you'll get an idea of how things worked in the COM world in products outside of VFP and why things are the way they are in .NET.
>
>I think John's post is accurate, but you need to get the basics down first. Databinding, Datasets, Datatables, etc.
>
>>You know, I guess I was spoiled with Visual FoxPro; it seems that Microsoft (and earlier with Fox Software) took such a simple approach to handling data that I cannot now understand how it is that this can be made so complex in .NET.
>>
>>Yes, I am complaining.
>>
>>I am pouring through C# books, and all kinds of other books, and I am telling you, there is no simple way to do data in .NET. Of course, admittedly, I am speaking from inexperience with .NET. I am still trying to learn C#, much less how to handle data. Still, data handling, in my opinion, is a much more complex matter in .NET. Why does it have to be this way? It seems that there is a multitude of ways to handle data, using LINQ, ADO.NET, and so on. I just don't know where to begin. I just ordered Murach's ADO.NET 3.5 with C# book to see if this might help me a bit.
>>
>>Also, a few years ago when I got into C# in some local colleges, C# also seemed cryptic to me, but it now seems much easier. I guess it is a matter of time and experience. I don't think it is this way entirely with .NET data handling. There seem to be many more steps to handling data, unlike VFP and other xBased languages.
>>
>>Okay, I am finished with my complaining for now. :)
>>
>>Does anyone want to help me complain, or perhaps direct me to a simple tutorial on .NET data-handling?
>>
>>Has anyone else on UT here felt just as frustrated as I am feeling, or did y'all get over it 3 or 4 years ago while I was still making money with VFP?