>>>Try to issue LOCATE after setting filter

SET FILTER TO ...
>>>LOCATE

>>
>>Is this supposed to be faster than GO TOP?
>
>It's a habbit from fox 2.6 days when LOCATE with FILTER was rushmore optimizable and GO TOP wasn't. I don't know if it still hold true for the latest VFP versions.

Yes.

Current situation:
* exists a index for the filter condition

GO TOP and LOCATE (FOR .T.) uses a ordered by TAGNO() scan

* exists a index TAGUSEDFOROPTIMIZATION for the filter condition
1 TAGNO()=0 ( TABLE order)

GO TOP use a ordered by TAGNO() scan
FOR condition uses a full optimized SEEK ( time is o(Log(RECCOUNT))

2 TAGNO()#TAGUSEDFOROPTIMIZATION

GO TOP use a ordered by TAGNO() scan
FOR condition uses a partial optimization ( time is o(RECCOUNT))

3 TAGNO()=TAGUSEDFOROPTIMIZATION
This is a important issue because
VFP don't see this as full optimizable !!!

GO TOP use a ordered by TAGNO() scan
FOR condition uses a partial optimization when it can uses a full optimization. Sin.

The workaroud is SET KEY.

Fabio