>Hi all
>
>I have a Parent-Children-Grandchildren form which the user requries to copy records of. In the sense that he is adding a record and he knows the previously entered parent record identification details, for eg. OIO no.
>
>My question is what kind of a UI should be provided. Also the parent table has children and grandchilren tables, how to manage the stuff in a expandable manner, even if I hardcode the name I would want to have some flexibility in terms of table expansion. Fields will be added and removed as and when required so except for FK, PK and OIONo nothing is predictable.
>
>Please advise.

Not sure what you mean by "what kind of a UI should be provided", Bhavbhuti, as you've already stated that you already have a Parent-Children-Grandchildren form.

If you mean how should the form be presented, I'd suggest a 3-page job. The granddad page would have a grid to select and, say, details fields. As you select a granddad, click on page 2 to see its grid and details, and so to page 3.

HTH

Terry