Hi Wally,

>It is really a big question that you ask. there are many potential choices and programming decisions that can be made to accomplish your task.
>
>When you have a child table, then it can be displayed either in a List or in a Grid. Grids are very alluring, but I've tried them and prefer lists. Many others prefer lists also. Grids have paint problems and other problems. You can use them, but many who've tried decided not to.

thank you for your answer, but my problem is not in the
parent-child relationship between tables, but in a such relationship
between forms (not only editing forms - universal forms).

Child form is "living" inside his parent (it moves with and within it,
shows/hides with it and dies with it). So what I need is a form
(GRANDPA-form), that can have child-forms (DAD-forms) and everyone
of these child-forms can have its own child-forms (CHILD-forms).

The GRANDPA-form is easy - it is a form with ShowWindow property
with value 2 (As Top-Level Form) or the main VFP window itself.
The CHILD-form is easy, too - it is a form with ShowWindow property
with value 1 (when the GRANDPA is Top-Level Form) or 0 (when the
GRANDPA is the main VFP window).

But I'm really missing the idea for the DAD-form - it must be both
the child (of the GRANDPA-form) both the parent (of the CHILD-forms).

Any ideas ?