>Hi Fabio,
>
>Grid.Optimize is same as BROW ... FILTER... But if you does filter 10 records from 3500000 by Index Expression, is GO TOP is slower than LOCATE FOR .T. - SET KEY TO is faster.
>
>MartinJ

Hi Martin,
not task is therefore simple.

Help say:

Note:
As with any data manipulation command that can impact Rushmore optimization,
you should be aware that actions taken against the Grid's data source could result
in behavior that differs from when the Optimize property is set to False (.F.).
For example, Rushmore optimization might trigger an implicit TABLEUPDATE to occur for a row buffered cursor. And an error may or may not occur depending on whether the record is blank or whether the cursor is a view.

This is a example, it is not the full description of the command operations.
Which are the other examples where can have behaviors that I must know?

The documentation cannot be written like a puzzle;
I understand that someone can be felt satisfied of knowing what the others do not know,
but does not have sense to make a product and to hold hidden the operations.

For the BROWSE NOOPTIMIZE i don't found this warning;
and, on Grid the default il Optimize=.F., on BROWSE is NOT NOOPTIMIZE.


Fabio