To me it is easier than to link parent and child grids, use SET RELATION, etc. I don't see a problem with adding, editing and deleting records in a view or cursor which is a grid recordsource. You manipulate the cursor records and just refresh the grid.

Hi Nick,
I tried to map out what you said and maybe this is the stumbling block:
I have built several systems using using the txtbtns class as basis for my navigation buttons. With that approach you click on Edit (or Add) buttons to make changes to data on a form, and then click on Save or Revert to save changes or ignore changes. I'll bet you make changes and they're automatically saved. If this is true, then it looks like that design decision that I made a year ago has come back to bite me.
Bill