but also for people like you who (correctly) promoted typed datasets as a lightweight way of passing data between tiers,

Kevin got that idea from me! <g>

~~Bonnie




>SQL 2008 offers change tracking/change capture, right there where it belongs....in the database engine. :),
>
>If it were possible for a database engine to manage change tracking in the context we've discussed, of course I would agree with you.
>
>In this context, change tracking happens at the app not the database, since only data that has changed is passed back to the database. The change tracking in SQL Server 2008 records changes but does not automatically manage this for you.
>
>In context, previous discussions here suggested that VFP people do care about this while many NET converts do not. You did post a "roll your own" solution using typed datasets against SP but I'm not sure whether you ever used that in real life. POCO seems to be strongly oriented towards people who do care about change tracking but also for people like you who (correctly) promoted typed datasets as a lightweight way of passing data between tiers, something that was a mess with EF3.5 and with L2S for that matter. But I guess we'll see.