Thomas,
If somebody has the luxury of starting fresh, it seems sensible to create reusable classes that work just as well in connected and detached/stateless scenarios and that conserve bandwidth. Why wouldn't you- especially if the development tool offers change tracking for that precise purpose? IMHO it's like using local views in VFP - not necessary, and a bit more complex than SCAN FOR etc, but when it comes time to upsize to a C/S database it's a no-brainer if you've prepared from the start.
The task is to figure out whether it is the SP or the change tracking built into datasets/eventually entities that offers the long term benefit. ;-)
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
