Carl Karsten wrote:
> Much like I want the database engine to make sure I don't create orphan child
> records, I want some low level generic code that makes sure database updates
> don't get overridden. I doubt I am the only one.
I agree with you, Carl, that Dabo should provide some basic behavior for
detecting and responding to collisions. Then, the application developer
can decide to override, circumvent, or expand on the basic behavior Dabo
provides.
Adding the list of fields to the where clause seems like a pretty smart,
generic way to accomplish this. VFP got a lot of things right, and this
is one of them. I don't see why it wouldn't work with all backends, and
anyway the app developer can set it to not detect but overwrite updates
if they choose.
--
pkm ~ http://paulmcnett.com
©2006 Paul McNett |
