>>George and others,
>>
>>LOCATE is faster than GO TOP when a filter is invloved because LOCATE is optimizable and GO TOP is not.
>
>Thanks Jim (and Fred too). Filters?? Who uses filters any more?< bg >.
>
>This does bring up a question, however. How can a LOCATE without an expression be optimizable? If there's no expression to optimize...

My SWAG would be that since LOCATE respects the FILTER, it uses a similar mechanism as the SQL SELECT statement does in matching the WHERE clause to an existing tag. How that happens, I really haven't a clue. :)