There is a known problem with using grids and a filtered data source. Microsoft recommends using SET KEY TO instead of SET FILTER TO. I don't remember the KB number, but if you go search Microsofts KB for FILTER and GRID you'll find it.

>>>hello,
>>>
>>>I have 2 occasions where I have a much slower grid ( and I know that I've done this before without a problem, but... )
>>>
>>>1. filters
>>>??? slow slow slow ( only ~20 records on test table )
>>>
>>>2. DynamicBackColor
>>>not sure why, there are only 2 iif() and 1 rgb() in the string, and only 20 records in the test cursor driving the grid.
>>>
>>>It's the same base table that drives these two problems. The filtered grid is a modal form that will always be spawned from the form with the DynamicBackColor, if that makes any differance.
>>>
>>>ideas?
>>>
>>>- jer
>>
>>1. Filters
>>Be sure your filter does not conflict with your sorting index. In other words, SET ORDER TO LastName and SET FILTER TO ZipCode = "23456" can be slow because each time you change go to the next record it has to check the table for the filtered value. With only 20 records I wouldn't think that would be much of a problem, but it can definitely be a problem with a few hundred records. You can get around it with some creative indexing.
>>
>>2. DynamicBackColor
>>Just a wild guess, but see if your test cursor is based on a large table. If so, add NOFILTER to be sure you're truely woking on a small cursor.
>
>all test data totals about 45 records.
>
>
>I just read somewhere about grids not optimizing the filter clause, use set key as an alt. tring to, but it requires a range and i want an "all except" type filter (key).