It can, but not when the filtered table is in a grid (don't ask me why). Also, you should try to avoid non-optimizable commands when you have a filter set like GO TOP, GO BOTTOM, and SEEK. Use LOCATE with no parameters for GO TOP. If you have an order set you can make it descending, LOCATE, then make it ascending for GO BOTTOM and LOCATE can be faster than SEEK with a filter set. These same guidelines apply when you have deleted set ON, a tag on DELETED() and lots of deleted records.

>Can the SET FILTER command take advantage of the Rushmore engine?
>
>TIA