Hi Jim,

Good Points. My only beef is with people like DC who take any chance they can get to make negative comments about .NET. I think VFP is a great product that is not marketed by the vendor. I also think that .NET is a great product that is marketed by the vendor.

As myself and others here have experienced, the real or percieved lack of support by the vendor for VFP dictates that this development tool has problems being accepted by many clients.

Working with .NET for the last three years, there have been zero situations involving Data that I haven't been able to come up with a solution for. The solutions sometimes take more coding than they would in VFP - but that code can be re-used again and again... It's just different, that's all.

Regards,

Al

>>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.
>
>I believe you misconstrue things here.
>I don't think anyone has said .NET can't "do data". What I have heard, and have no reason to doubt, is that it is a real chore to do data in .NET and that often one has to find alternative designs to do what is so easily done in VFP.
>
>Surely you must see that the very existence of "LINQ" speaks to that very issue.
>
>cheers
>
>
>
>>
>>
>>>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...
>>>>
>>>>
>>>>
>>>>>>Perhaps you did'nt explained the point well enough :-D
>>>>>>
>>>>>>LOL! I think the content of the link sort of speaks for itself....
>>>>>
>>>>>Kevin, Kevin, Kevin,
>>>>>
>>>>>There seems to be some frustrations left. The sad thing is that we'll never know what it is exactly.
>>>>>
>>>>>Perhaps it's because even if you're an MVP and makes tons of money with VS.net and C# you can't get over the fact that it'll take a while (perhaps many years in fact) before you're able to process data as easily as you did with VFP.
>>>>>
>>>>>Perhaps it's because you still see many others who are able to make a nice living working exclusively with VFP. Should'nt they have to suffer like you to process that data <g>.
>>>>>
>>>>>Perhaps I put my finger exactly where it hurts. Perhaps there's something else.
>>>>>
>>>>>Anyway I'll take myself as an example. When I don't care about something I don't speak about it. Why waste time on something meaningless to me. To you VFP should'nt be used no more in any circumstances. Still you continue to bash it. What's your beef? Should'nt you forget about VFP and go on with your life.
>>>>>
>>>>>I really think that there's still a wound that needs to be healed.