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.

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?

I guess I can get verification by commenting the TABLEUPDATE() commands for the Child tables in the Save button, creating a new parent/child records, and clicking the Save or Close button. The Parent record will be saved(TABLEUPDATE()) and the related child records also????

I have to test this at home because these little apps are part of my own contracts - not my day job.

Thanks for your comments.

Regards,

Paige