I'm not sure you need a TableUpdate() with row buffering and UPDATE-SQL. However, I would trap the changes to the parent and child tables inside a TRANSACTION to be sure that I'm not left with a data integrity problem if the change to the parent succeed but the changes to the child fail.

HTH

---

>I have parent and child tables - both with pessimistic row buffering. Based on changes to a record in the parent table, I issue an UPDATE SQL statement to update child records [on multiple fields]. Do I need a TABLEUPDATE command after the UPDATE? Should I use a TRANSACTION to avoid record locking problems?