Hi Erik ---

>It's probably not the most desirable, but I force the user to deal on a child by child basis. IOW, before adding grandchildren to a different parent, they have to save the ones they were adding. IOW, it becomes a parent-centric process instead of a grand-parent centric process.

I'd hate to do that. I'm kinda steering that way now but it'd break the UI metaphor for the application that I have established, which is Apply saves all changes to all, Undo reverts all.

>But here's an idea if you don't like that: Define your grandchild view to hold all of the forms for all of the steps for a given process. Then set filters when switching beween parents. This way all of the records stay in the same cursor, with no need to commit when switching Process steps. When the user is ready to save everything, remove the filter and TABLEUPDATE().

That's an intriguing idea. I think I'll try that one. How about this, I have been considering using TRANSACTIONS when the edit starts and either END or ROLLBACK as appropriate when the user hits Apply or Undo. What do you think of that?