OK. Why not tie the save option into child data entry action. If you don't specify a workarea in the save button (the * option), it will save every workarea with uncommitted changes. When your user has entered the first child record, they hit save (or you programatically save if the form passes validation) and both the parent and child record is saved at the same time. Thereafter, when a new child record is created, the save option only saves the child record because the parent is already saved. By doing it this way, when a new parent and the first child record is created, if they decide the abandon the first child record, they parent can be discarded too, no harm done. If they carry on, they are saving after entry of each child record so no chance of hundreds of uncommited child records.