>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?
>
>What is the regular way of solving the problem of displaying object properties of many child objects?
>
>Thanks for your help in advance!

I've rearranged your questions a little.

If I were going to set this up, I would have a Parent object with a reference to a single Child object, as opposed to having many Child objects. The Child object would be responsible for several actions, such as getting all children
for a parent record, getting a single child record for editing, and so forth.

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

Conceptually, yes. Assuming you are doing this in VFP, you would have a cursor that can be used as a source for list boxes, grids, and so forth.

The answer would change if you were using ADO. Although you'd still have the objects constructed the same, you'd need to use an ActiveX grid (as opposed to the native VFP grid) for multi-record display, as the VFP grid will not work with ADO recordset objects.

Hope that helps.