George,

>>>> I know for sure, that if Filter filters only small amount of records,
>>>> grids become painfully slow.

>>> But she's using a query first of all. Second, I've never had a problem
>>> with using filters with grids.

>> How many records were in your original recordset and how many records
>> were after filtering? In my experience, if, say, I have 10K records and I
>> filter only 20, all operations become so slow, that it's almost
>> unbearable...

> That's why you query rather than setting a filter when using a grid. This
> applies to almost any control (such as a list or combo). While they're not
> nearly as sensitive to speed dregradation caused by setting a filter,
> they're not nearly as complex as a grid either.

Nadya is correct when she states that filters can dramatically slow down a
grid's performance.

Furthermore, there are instances when you have to use a filter and cannot
query again. For example, if you allow the user to change multiple records
at one time and view the effects of the changes on a particular subset prior
to saving or cancelling the changes. This type of interface is often
encountered as a requirement when you develop software to evaluate scenarios.

Daniel