I'll second that. There are a lot of things I really like about dotnet. Data manipulation is not one of them (yet). Simple enough to do, even with multiple layers. However, If I'd never used VFP previously, then it probably wouldn't even be a blip on the radar. The problem is, I have, and I expect more. Maybe one day. Right now, if you need to manipulate query results, subqueries, and cursors, then linq query in memory is the only efficient way to accomplish that (that I know of) that comes even close to vfp (not to mention that other linq providers for relational data stores is in the works).

(I did not write that to start the L2S discussion all over again. Just making a comment on data handling and manipulation based on my limited experience and knowledge.)


>Don't assume anything. You can connect multiple back end databases, but sorting, etc is done differently as you get ADO.NET datasets. Moving to .NET from VFP requires a mind shift in some areas. Data manipulation is one of them.
>
>
>>I make extensive use of local cursors because of disparate back ends, e.g., databases on Unix and MS SQL Server that constitute the overall "database". Awfully useful to be able to bring down result sets from different databases and then continue to use both SQL and VFPs own data manipulation to present the data. Like a lot of VFP folks, I build indices on the fly for sorting grids with header clicks, etc.
>>
>>I assume the same end results and speed are available in .NET once one gets used to it's programming model.
>>
>>Gary