>VFP 9 Help says following:
>"When using SET FILTER to filter data in a grid, use the SET KEY command to increase grid performance."
>Does it indicate that performance problem still exists?

It doesn't mention the new Optimize property in VFP 9. Does that mean we shouldn't use the new Optimize property? The docs are not the only way to decide how to do things. SQL Select does not use SET KEY. Does that mean SQL is slow?

SET KEY introduces other problems. :) To filter a table 3 index tags can provide 8 possible combinations. To do the same with SET KEY would take 8 complex/compound index tags.


>
>>I haven't used filters for a table of any significant size in ages. Love those parameterized views. However, I could swear that I recently came across something that was saying that in VFP 9 (or whatever it said - a recent version) the filters were now very fast and this made them useable again. Wish I could remember where I saw that (or perhaps I was hallucinating). Have you heard anything like that (I guess not based on your reply).
>>
>>>Then this is your problem. Grids and filters don't agree with each other. In fact, SET FILTER command is obsolete and should not be used at all. Look into parameterized view or CA solutions instead.