Hi Denise!

OK, here's a thought: Leave your main nav bar only affecting the parent table. Have OK and Cancel or the equivalent save/revert both parent and child. Wnder or alongside the child grid, have separate buttons for child-add, child-delete.

I am assuming the grid is enabled.

Is this paradigm OK? Essentially, what you're adding and deleting will be apparent by the placement of the buttons and OK/Cancel will save/revert all changes since last save. This is more-or-less expected behavior anyway.

Did I understand this correctly?

>Well, I did some poking around with my earlier problem and found that my child grid was updating and reverting just fine when I used the main navbar on my form. So apparently the buffering and all is working fine.
>
>But what I need is 2 navbars. See, I don't want to allow the user to add a parent record but they can add as many child records as they want. When I click add on the main navbar I get a message asking if I want to add a parent, a child or both (but for some reason the both was disabled). Well, that might work but it's not clean enough.
>
>So I figured I'd just put the grid and a navbar in a container and then the navbar in the container with the child grid would just work on it. Not! :) Whenever I clicked add on that child navbar it asked the same thing (parent, child, both).
>
>What I really need is for the navbar in the container with teh child grid to act independantly of the parent table. I need to be able to add child records without that message coming up. I also forsee that the user might be editing a parent record, add something to the child, decide that they shouldn't have added it and click "revert" and lose all the edits they made on the parent record as well.
>
>So I guess my question is how can I make sure that the main navbar only works on the parent table and associated fields and that the container enclosed navbar only works on the child record and that grid? Thanks!!