no, you need create only a Children Business OBjects, because the Children is the object for manipulate all the children, are you usign a Framework?, because many of this funcionality exist in frameworks n-tier.

if you work with business objects is better work with views.

Best Regards

>Hello,
>
>In my new application I try to use business objects that represent the entities, and these will be responsible for the data handling procedures as well as the user interfaces.
>
>I have one question:
>When I have child records, like many children for one person, they should be instantiated as objects on the Person class?
>
>How do I then display the children in a grid for example, when I want to bind the user interface objects only to the properties of objects instead of tables?
>
>Should the child class then create a record in a temporary table, that I could then use as source for a list or a grid?
>
>What is the regular way of solving the problem of displaying object properties of many child objects?
>
>Thanks for your help in advance!