Mike,
What I usually do is timestamp the record. If the timestamp doesn't match when I update the record, then I return an error message saying the record has already been updatedYeah that would work, but there's still a "human" intervention that would not be necessary with decent change tracking. The whole system seems designed for 2 tiers until MS delivers the promised changes.
"... 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