>>>Are you serious? .Net would be a loser just from the start with this >>workflow (and I have done more than booting up to .Net environment). Just >>benchmark retrieving 1million records from SQL server and you'd stop >>there. Make that 2millions, worse, make that 20 millions and voila you >>need extra workarounds if you didn't think of it from the start. VFP >>wouldn't bother unless physical size is over 2Gb.
>>>PS: I use all of them (VFP,SQL server,C#) and I find comparison >>unnecessary. On an overall comparison (and that means there would be >>items that you can't do in VFP without getting help from external sources >>heavily) .Net would win but not in data processing arena (and it's not a >>myth, fact).
>
>Hi Cetin
> This assumes that we would be downloading all 2,000,000 records. That is not the criteria. We will be selecting some data to work with and processnig that data on a client.
>
>This is not a what's better exercise just an exercise to show how you manip data in .NET and VFP. I see this as a group education type of process.
>
>Thanks
>Rodman

BTW if you want I have a simple data processing code both in C# and VFP that I created long ago. The task was simple and VFP was faster over 200%. VFP code is optimized and C# was optimized to the point I could do then. If you would play with its optimization I can find and send.
PS: I don't believe such tests have a great meaning and just a benchmark with a certain task (in real world apps we do more than that).
Cetin