I think that that maintaining separate index tags (one for name, one for SSN, one for HN if you want) is the way to go. You can instantly change to the tag of your choice, do a lookup, then switch back to the Name tag, and refresh() the listbox. Piece of cake. BTW, I feel differently than Craig about potentially using too many items in your listbox. I really like the "instant scroll" that a listbox gives relative to a grid. However, I do agree with Craig's suggestion because of the current bug in VFP regardling listboxes (the Item#253 problem). There is a workaround: this problem does not happen if you use use RowSourceType=9 (popup) and use a DEFINE POPUP with a PROMPT FIELD clause. Overall, though, I think you will probably be happier using a grid.

If I'm not mistaken, there is already a ready-to-download picklist class (or two) on UT that already contain 90% of the functionality you need. Why not subclass and be done with it?

>Here is the behavior I had envisioned, though I could do something
>different: I saw the list box being sorted by name at all times and
>displaying the same columns in the same order. A separate text box on the
>form would allow the user to enter an SSN, and a button (or simply the
>text box VALID) would search the table for that number. If found, I would
>like the matching record to come up selected in the list box.
>
>Don Smith