>>>Moises,
>>>
>>>You should only use filtered tables and grids if you have very small number of records total on the order of a couple of hundred rows. Beyond that the performance of the grid will truly suffer. You will also have to deal with the vertical scroll thumb will not go all the way to the top or be sized relative to the number of rows. Parameterized views do not suffer these problems.
>
>>are you saying that if i am outputting a report from a table
>>with (say) 358 thousand records, that performance will be better if i
>>base the report on a parameterized view of that table as opposed to setting
>>a filter on the table and using the table itself ?
>
>Patrick,
>
>No. I highlited the part of the message above where filters do not work well. Filters on all but small tables displayed in grids perform miserably.

David
I agree with you if you try to exclusively set filter to a big table, but not if you use set key beforehand. I have an application where a grid browses a table ( 300k records ) directly. I first use set key for the first subset to be shown ( that's where set filter shows very slow performance ), but then i activate any filter condition i want, and it's very fast!
Cheers,
Jaime