>But that;s the point.In .net you pull the data and you populate the control - seperate steps.

The same is in VFP (when you work with SQL Server, or any other DBs, BTW working with with NATIVE is the same, just hidden and easier:-))


> Get all the data in one trip, then populate the controls. ADO works differently from Fox. There is a lot of power in the disconnected nature of ADO data. You can return multiple cursors with a single sproc - one trip to the server - and then fill multiple datatables from that sproc from which you fill your controls., It is more efficient than 25 trips.

I didn't see ANY difference here than VFP. SP is programed on server and it returns resultset based on parameters you passed, no matter what your FrontEnd is.

>One of the big myths that has lived in our community for too long is that Fox "handles data" better than .NET. Just isn't true. I handles it differently and there are strengths and weaknesses on both sides, but once you really get your head into the .NET way of doing things you'll find the advantages can be very great.

Agreed. But ALL controls in VFP is DB designed. So you have to changed two or 3 properties (VISUALLY) and all done!

Don't get me wrong here, I am not against .NET (And I'm always against the discussions which is better). Just some things are easier to do in VFP that in .NET (at least for me)).