Dan,

If you have SET DELETED ON make sure you have an index on the expression DELETED(). Are you using a grid to display the filtered table? If so it's just going to be horribly slow. You can use SET KEY as one alternative. I'd lean towards a parameterized view myself.

>I have a single character indexed field that is used to split a 2 million record table into 4 categories. I have check boxes to turn on what segments of the list are visible. The filter does not appear to be utilizing Rushmore. It is very, very slow. Setting the filter in the index would expand my required index from 8 to 120!! (every combination)
>
>I've tried the filter with INLIST and with a simple "or" statement.
>
>Any Suggestions how to filter to data without restructuring the database or using Views?