SET FILTER will always be slow when the resulting set contains very few records from a big table. You can test this from the command window: issue your SET FILTER for Chicago, and then BROWSE.
Can you replace SET FILTER with a SELECT SQL in your option group?


>I have the following situtation. I have a table of approximately 121,660 records which have a region field. It is populated with either WDC (Washington,D.C.) or SFB (San Francisco). The records from DC total 71,448 and 50,204. The remaining records are for Chicago approximately 5. On the screen I have a optiongroup that will set a filter for the different area. All seems to work well for WDC and SFB but I am having problems with Chicago. The code set the filter, does a locate and then refreshes the grid. On the Chicago selection when I try to refresh the grid it just takes forever. Is this because it has to navigate thru the table or what. Any suggestions.