>The default for the Force parameter is .F. and I don't set it to .T.
>
>Here is a scenario that could occur that has prompted this question in the first place:
>
>Both User1 and User2 are modifying Product AAA.
>User1 changes the Product Description (parent view)
>User2 changes the Quantity of a line item (child view)
>User1 and User2 both issue TABLEUPDATE(0,'ParentView') and TABLEUPDATE(1,'ChildView')
>
>Both users changes have now been saved to the base table. This is what I'm trying to avoid. Any ideas?
>

You may want to implement a pessimistic buffering scheme in this scenario.