>>You think Kevin and Craig are independently wealthy and don't write systems? Again, they have taken the time to put the money where their mouth is; to date all we have is your mouth. They make great contributions by giving of their time to the public, code camps, user's groups, etc. What do you do that gives you the right to belittle them or their efforts?
>
>You might want to start thinking about what I'm saying or suggesting. You might want to pick up the challenges I throw arround with code examples. For example did you evaluate the SET ORIENTED vs RECORD ORIENTED example (see my reply to Fabio) where a SQL statment is compared to a VFP RECORD ORIENTED approach. Evaluate and you might learn something. However, my experience is that no-one is really able to refute it or is too embarred to answer it.
>
>But to do your a favour, I'm seriously thinking of starting some messages doing some show cases build out of older material that is already present here on the UT.


Again, can you read? I could give 2 craps about a comparison of VFP and .net's data handling and set/record oriented. Its the same as driving a car. I don't have to worry about what sequence the injectors fire or how the oxygen sensor retards combustion, etc. I just turn the key and drive. I don't have to worry about how the sql engine does its magic, only that I write my stored procedures to get data and I get data. Voila! I have done a lot of work with huge amounts of data in .net and find that ado on par is just as fast as VFP when handling data. The problem with VFP is that most of its users rely on bringing down huge amounts of data and then munging it, almost the equivalent to spaghetti code programming. The real finesse is using stored procedures and transact sql to bring down only enough data to get the job done, which requires little munging on the local machine, ergo no need for local data engine. Mention the lack of local data engines at .net code camps and people look at you like you've got a third eye. Mention the push to have local engine in .net, they laugh. Its really funny. No one in .net worries about it except for people who can't manage to write decent sql to get the data they need, in the format they need without the need for huge amounts of processing on the local machine.