>>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).

You're right. I was working on an old 2.6 app yesterday and stuck in that mode. My advice was fine for BROWSE but so-so for GRIDS. Sorry. Still, I can't imagine the filter causing such a slowdown on a 45 record table, I've used filters in a grid with looking at a table 220 records with no problem. If the real table is going to be larger than your test table, you should consider another solution, a parameterized view might be a good choice.