Don,

Yes and no.

Yes if buffering is set to 2 or 3 (record level buffering).

With table buffering (4 or 5) moving the record pointer will not trigger a tableupdate.



>Am I correct in my belief that TABLEUPDATE is called automatically when the record pointer is moved off of the current record if row buffering is enabled? What about child tables when the record pointer is moved to a new parent record? It seems to not work in this instance.
>
>Also, what else other than an explicit call will trigger an update trigger?
>
>My app is firing the update trigger multiple times when I move the record pointer, even if no edits were made.
>
>Thanks