Hello Nancy,

Thanks for expanding on your response. Actually my application is not that complex. I'm working on several apps: an insurance verification which has a parent record(the insured business) and children(various policies - fire, theft, flood, etc.) and a History table. Typical - Row buffering for the parent, Table buffering for the child table/s.

But the app that dosen't seem to be addressed in my research is a simple tracking/scheduling app for home health care workers. There are parent/child records because there is just too much data to for one table: name/address/etc. in the parent and skills(RN, LPN, HHA), dates for CPR, Physical etc. in a child, area, location, preferences (pets/smoking, etc.) in another child record. A ONE TO ONE - NOT ONE TO MANY. Hence maybe Row buffering for all related tables is more appropriate?

And if Row IS used for all related tables, and the parent record is saved via TABLEUPDATE() or the pointer in the parent table is moved - is the child records saved? I now execute a TABLEUPDATE() on each table - parent and all child.