SET FILTER is not rushmore optimized when you use grids.

>I have a form with a grid.
>
>The record source of the grid is a table "ITEMS".
>"ITEMS" has Indexes:
> Status (could be "I","R" and a few others)
> Entered_date
> Description
>
>The data has a filter on STATUS
>
>AND have the option to order the records on the grid by:
> Entered_date
> Description
> No order
>
>This is my problem:
>
>When the status = "I" (grid filtered on status, "SET FILTER TO status = 'I'") the navigation in the grid is pretty quick regardless of the order, but when I change it to status = "R" and the order is "entered_dt" or "description" the navigation gets slow but when I go to "no order" then it's fast.
>
>
>There are around 55,000 Records in this table. About 22,000 are status = "I", 8 are status = "R" and the rest are made up of other statuses. This slow response only happens when status is "R" and has order "entered_dt" or order "description".
>
>Maybe somebody has any wild ideas about why this could be happening.
>
>Thanks!