John-
I suspect I'm beating a dead horse, here, :), but the point is that a browse *seems* faster because the filter is applied only to a portion of the cursor. For a grid, the filter is applied to the entire cursor.

So, for a grid to be responsive like a browse, you need to use a parameterized view, and, probably, look at Fetch Size.

>With all due respect to everyone here, my original point was that performance of a grid with a FILTER should be somewhat comparable to the performance of a BROWSE with a FILTER. Here is my reasoning: