>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.
>


I'm not using a framework at this point. I want to try this myself in order understand the way of doing this better.

So the childrens object does not more than to handle the view (set the parameters and requery and update etc)? This means I do not need to store the field values in properties of a class, and the data entry and visibility will be done directly on the view?

I had the idea first to do all things on properties of classes and let the class do the translation to the data.