Actually, searching will be very easy. The mechanics aren't a problem, how to present this all to the user is. The child records all contain a foreign key reference. The actual structure is that the main table represents a label template, and the child record are all the part numbers which can be printed with that template. The existing search allows the user to enter part of a template name and it returns all matching templates, the user can then pick which one they want - no record by record skipping here, this is a SQL Server backend. The existing search button opens up a seperate form that is passed an object parameter containing the name of the parent form - thus when the user selects the desired record, the parent form query parameter is updated and the form is refreshed before the search form closes - no views, either, I'm using DataClas/VFP. It's a relatively simple matter to make another search form that allows the user to enter a part number, query the child table for that part number, and use the foreign key to update the parent form. The slight complication is that each part number can appear up to 3 times, with a different label type field, but it's no big deal to present the three options to the user in a grid and use whichever FK the user selects.
So back to my original question - you method is to present the user with a prompt when they click the search button and then activate the appropriate form? It makes the object reference back to the original parent form a little more complicated, but it could be done. Hmmm...

>
>In our forms with have a simple special form with few option buttons, which allows to choose Search Type.
>
>BTW, how do you plan to search in Child Grid? If it's a view, it would not be a problem, but if it's a related table, it's almost impossible.