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