My intent was not to get into a war of words. I was just simply tired of reading another post here effectively saying that .NET is not very good with data. And I happen to disagree. Simple as that. You are certainly entitled to your opinion and I respect that.


>And what I'm saying is that you draw incorrect comparisons between products and then get all amazed when people point out the errors. So .Net does data, so what. So .Net connects to SQL and Oracle, so what. So does VFP. So what is your point again? That .Net can handle data (via third party tools)? Great. Excellent stuff. Here's a news flash - we all know this already.
>
>Plus, your comment "If you do your most intensive data crunching with SQL Stored Procs in a well designed database - in many cases it can be faster than VFP..." - why would it be faster than VFP? If you use stored procedures then the backend database+server will determine the speed of returning the result set, not the frontend .Net or VFP application. This is another erroneous comment and comparison.
>
>And the comment "It obviosly does not have a propietary database that is part of the product like VFP - but who really cares" - well you can dismiss all the aspects of VFP that make it what it is and then indeed you will find nothing special left worth having.
>
>
>>What I'm saying is that .NET can do data. It obviosly does not have a propietary database that is part of the product like VFP - but who really cares. .NET can do data with many data sources - I've been using primarly SQL Server and lately some Oracle.
>>
>>So many people here seem to think that there is no other product on the face of the earth that can do data. And that is simply not true.
>>
>>
>>>This is the same erroneous comparison that is made all the time. You are not comparing .Net with VFP at all. You are comparing SQL with VFP. VFP can use SQL just like .Net and also has its own native dbms which .Net does not have. Apples and oranges.
>>>
>>>
>>>
>>>>I occasionally poke around some of the threads here and this topic seems to be raised alot by those who still use VFP exclusively. I once used VFP exclusively - up until about four years ago. I just don't get this arguement that .NET can't do data. It is simply not true. It's a huge lie. Sure, it is different than VFP - but .NET can do data and do it efficiently with SQL Server. If you do your most intensive data crunching with SQL Stored Procs in a well designed database - in many cases it can be faster than VFP...
>>>>
>>>>
>>>>