Not to argue anything Josh (or JohnK or Dan), but with 35,000 records anything optimizable, including a straight SQL Select, will do nicely here.

Cheers,

jim N

>John,
>
>I'm with you and Dan on this one. The reason for the speed difference is that filters are not rushmore optimizable when using a grid. That means that with a filter, each time you try to move the record pointer VFP scans the table to find the next record that matches the filter definition. With the view you'll get very fast requeries if your criteria are optimizable. Once the view has been requeried you can move within the view instantly.
>
>>Hi Jeff.
>>
>>Dan is right: A parameterized view will be MUCH faster. Try it, you'll see.
>>
>>>I have inherited a system that uses Filters, I have always stayed away from filters because they were always slow. Well now my users are compaining about the system being slow when I update the grid (another thing I am not to fond of).
>>>
>>>My question is what is my alternative to filters to let the users see only a subset of the data but will provide the some speed when switching subsets?
>>>
>>>I have not used views but that is a select of the data so it should not be any faster. I could build a table and set a relation to show the data but then how would I let the users sort the data in the grid?
>>>
>>>Some background info:
>>>
>>>35,000 records
>>>set filter to fielda = a and fieldb = b and fieldc = c
>>>indexes on major fields
>>>
>>>for the filter I have an index like this:
>>>index on fielda+fieldb+fieldc tag tag1
>>>
>>>Thanks for your suggestions
>>>
>>>Jeff Whitaker