>Hello Rich,
>
>Yes. The relationship between the parent/child records is set in the database and in the DE and appears to be working without any problems. It seems logical, as you say, that with the Relationship setup properly that movement in one table MUST cause cooresponding movement in the others. Obviously this can be observed in a browse/grid that contains fields from more then one of the related tables.

Ok, I never got that you had a relation set. Yes, if you have a relation set, movement in the parent causes movement in the child. Which causes automatic updating in both. If row-buffering.

>The question is: does a TABLEUPDATE()in the Parent table consitute a 'movement' in that table thereby causing a 'save' in the related child table/s?

No, TABLEUPDATE() in the parent is not movement of the record pointer, and no, TABLEUPDATE() in the parent doesn't cause a TABLEUPDATE() in the child.

HTH,