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 happy with the keyboard/mouse. See why I'm sort of lost? I don't know how to get the paramter to do that. For that matter, I'm not sure even IF it can be done...but it would make my app a bit more user friendly and forgiving if I can find a way to do it.

>Pardon me, but it sounds like you don't really want 100 records on either side of the target record, but, rather, a range of values for a field that includes the specific value the user selects. Is that correct?
>
>If so, then you just simply build your parameter to base it on a range that you calculate based on the user's input?
>
>>I know that I can do that, but it still won't give met the result's I'm after.
>>
>>For expample: A user has a 'vendor' screen. They enter the 'paramter' - let's say the Vendor number. They enter 500. Right now my parameterized view will use "VEND_NO = ?lcVend_No" (and lcVen_No is 500). So, I get the one matching record (500). But I want vendors 400-600 - the 500th and 100 records on either side. Make sense? So in this case it really doesn't matter what the ...snip