But you are still living on the whim of MS to decide when to focus on the next iteration of data access technology,
leaving your old apps running but getting no more dev love from MS side.
As the source is often not available when using pure MS tools, you have more problems after that point in time -
which balances the ease of starting compared to developing your own data access classes.


>LINQ to SQL and EF both create SQL statements, and pretty darn good ones.
>
>>Neither is SQL ;-) I meant the query method/language as in screwdriver vs. hammer.
>>
>>>As for local cursors, there are times when they are useful, but having to pull so much data across the wire to resolve the query is not efficient either.
>

Call me oldfashioned, but such data belongs onto the disk, even if it is a mSDHC:
RAM should not be thought of as limitless resource, esp. on mobile platforms.

>You can do this in .Net too.
>
>>
>>Yes, but you can also remember already sent over pages via caching or
>>cache and query with timestamp info, thereby lessening data transfer.
>>Rowversion info or atomic timestamps are good ;-)