>Would the arrangement you both suggest support editing in two child forms at the same time?

Not quite sure I totally see your requirement but let me put it this way. The formdatachild (that Mel suggested) is natively modeless. So, it can be pushed into the background, left open, whatever. A good analogy for this form class is like a pageframe. You could have two pages in a pageframe and have two different records in each page of the pageframe. The formdatachild can be thought of a little like each page in a page frame, except, that in a pageframe, you can only see a single page at a time. With the formdatachild, you can see as many "pages" (forms) as you like. So, if your CDE/DE supports numerous (child) cursors, you could have many child records open/edited at the same time. However, I have a feeling you are referring to having more than one child form editing mutiple records from the *same* table/cursor -- correct? If that is the case, then you will need to take a different approach. The child forms referred to both inherit the parent form's CDE/DE. They do not have a CDE/DE of their own and therefore, they do not support the use of their own "private" data session (that could contain different records from the same cursor source). They natively operate with what you have in the parent form, no more, no less.

>so the question is: would Codemine be nice enough to replicate the environment of the parent form in the child form's private data sessions?

See above. These child forms do not support the use of their own private datasessions as far as Codemine is concerned -- they inherit the parent datasession. Therefore, a different approach would be required. I can think of a way to achieve what you need in Codemine. Let me know if I have understood your requirement correctly and then we can discuss a solution.

Best