>I have a grid that displays a filtered set of records from a relatively small table. Unfortunately, the grid scrollbar does not respect the filtered set of records and instead updates itself based on a record's current position in the unfiltered view of the table. This can look pretty whacky.
>
>I have a hunch that this is "by design". Any way to fix this other than using a SQL select into a seperate cursor? Normally this is the way I would do things, but in the situation at hand there are many controls on a page that can update fields displayed in the grid. Thus I was hoping to use a filtered view (USE AGAIN) of the same table being managed by the form vs. writing complicated logic to forward discrete updates to the grid.
>
>Thoughts?

It has always worked this way. Even deleted records count - just try to delete first 50% of records in a table and do a browse, don't even need a grid for that, and you'll see that you can't pull the scrollbar to the upper half of its space. The scrollbar uses the position of the visible record relative to reccount(), period. It would be just damn too slow if it counted visible records each time. And if it did, you'd have no clue that there are other records.

So... an updatable parametrized view, or a simple cursor with properties set so that it would be updatable, is your ticket. Or, simpler, just tell your users that the scrollbar respects invisible records.