>Jim,
>
>Actually, this works without any changes to the Framework! As in your code sample, you *can* call the Business Object's Save method, passing the nRows and lForce parameters:
>
>This.Save(1, .T.)
>
>The values are passed on to the Data Behavior object which in turn issues a TABLEUPDATE using the parameters you have passed.
>
>Regards,

Kevin,

I realize that this will work. But if the developer could set a property, say, bizobj.nRows and lForceupdates is false, then if the developer defines table buffering, and a user makes multiple changes to the cursor, the databehavior obect could scan the buffer one record at a time using the getnexmodified function. If another user has changed the data, the user could be given the opportunity to revert the changes or overwrite what's currently on disk. The bizobj could even use the curval() and oldval() functions to display the orginal and current data, giving the user a basis for a more informed choice.