>>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'm aware of that. For long time SET KEY was recommended as an interim solution for those who wanted to filter, but could not use SET FILTER with grids. My point was that this Help notice indicates that MS still recommends to use SET KEY in this situation. Maybe it's just a leftover, I don't know because, personally, I don't use both commands.