>Hi,
>
>Thanks a lot for the illustrating codes.
>I think using view is not wrong ... it just does not help to make things any easier in this case.
Views have their limitations, and you just hit one - though, there's not really a way to handle your need using anything out of the box.
Just an idea - you could have a scatter name object for the parent record (the "one" side), and an array or collection of such object for each child record. Then you could just generate a bunch of controls for each of the properties of these, with their names somehow generated, and the save operation would consist of simply doing a gather name from each of these objects.
May work. Haven't tried, though.