Thinking in VFP application and data manipulation terms is a road to failure in .Net. Some things carry over, but lots of things don't.


What specifically do you not understand about LINQ?

EF is definately for accessing the DB. Further posts make me think a simple object will do the trick. Heck a Dictionary might work just fine.


>At the risk of coming over somewhat thick, I still don't have a clear view of your specs. That being said, I guess that in VFP you would use sql to compute aggregate statististics, sorting and filtering on single tables (i.e. no joins). You'll find that that functionality is available with datatable, and as I said it's conceptually the closest to what you (I?) are used to. If worse comes to worse you can always scan the datatable sequentially (Hope they don't kick you out of UT for this kind blasphemy :) ). As I said if you know a recordset in ADO or DAO, well datatable is pretty close to it.
>
>LINQ is a riddle to me. Each time I (try to) use it I wonder what they thought was wrong with sql. I'm sure it's sooo much more powerful, but for the vanilla vb programmer it's a challenge.
>
>I may be wrong, but E/F is more for accessing the DB.