Hi Niels,
Yeah, I've been looking at it, and I can see what's going on, and I may be able to fix it, but...
In a more conceptual sense I'm wondering about the place of "browse children". The whole concept on a browse having children makes the browse into a container, and the browse doesn't make a good container (that's the Form's job). So there are going to be lots of edge cases where the child-browse approach will struggle, while the Memory-form-contains-multiple-browses approach will work better.
In the longer term I may get to deprecating the "children" approach - it adds a lot of complexity to the architecture of a page, without adding a lot of benefit. Food for thought.
cheers
Bruce