Yeah, I thought of that to, but what if "Thomas" is the first last name beginning with the letter "T"? Then they won't be able to go backwards, just forwards.

>Well, you could trim the parameter. So, for example, if they enter "Thomas" you could query for LIKE "Thom". If you keep getting zero record sets back (to "Thom", "Tho", etc). You could even keep trimming the string until it's just so silly you can't go on < g >.
>
>>Yes, you are correct. The example I used really isn't a good one though I guess. I really want it to work for customer names. A user enters a 'T', then a form with all the last names begining with a 'T' pops up. (That form has a view that uses the "Like" gizmo) So they select 'Thomas'. The 'lookup' form closes, and now there back at the customer screen. That view is requerried with the selected 'Thomas''s primary-key parameter - thus returning the one record. What I'd like to see the user be able to scroll through a few of the records on either side of 'Thomas' in case they selected the wrong one or something, like they were really looking for 'Thompson' and just got trigger ...snip