>When I use an UPDATE I want to issue TABLEUPDATE() afterwards, but it may not
>be on the record that has just been updated, how can I ensure that a view that
>I UPDATE is COMMITTED.

By using TABLEUPDATE(1) or TABLEUPDATE(2). Those both update every changed record in the table, but handle errors differently.