I had to do something similar for an inventory system. I had a single search button that brought up a search form and on the form I presented the search options. The users preferred it to two separate search forms and/or two separate search buttons on the main form or tool bar. It was fewer keystrokes overall. One search button which opened a single search form and they entered the search condition in the appropriate field made them happy. The search form had fields for the search conditions. I think it depends on how many conditions for searching you have to present to the user. In my users case, the fewer clicks or keystrokes the better.

Tracy

>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