I would create a second Form entirely for this, with a separate Private datasession. Also, you will have to 'reverse' the Relation to create a relation from the Child into Parent, probably just a simple one-to-one relationship...it's actually many-to-one but they can't search as easily that way.

Also, realize that many Children can have identical IDs but different Parents, so the users will have to choose which one they want.

HTH,

-Irv.


>I have a form which displays a header record and related child rcord in a grid. Currently there is a Search button on the form that allows he users to type in part of the contents of one of the master fields and search for the record, which then loads the header and grid with the proper record and children.
> The users have asked for an alternative search that searches by entering one of the child values. How would you go about implementing this from a UI standpoint? A second search button? Distinguished how? (The current button is a graphical command button with tooltip text) Make the existing search form more complex and allow the user to enter one or the other search criteria? Some other way I haven't thought of yet?
>
>
> Randy