Seek is always a tiny bit faster, for the reason you noted. The instance when LOCATE is more appropriate is when you need to use CONTINUE. IOW, if there are multiple records that you need to find that aren't grouped together in the current index tag, you can find them all with LOCATE and CONTINUE, whereas SEEK will only find the first record that matches your SEEK expression.

>Is there a rule of thumb for using Rushmore as
>opposed to Explicit indexes, i.e.
>

>SELECT Customer
>SET ORDER TO 0
>LOCATE FOR CustId = "12345"
>
>       vs.
>
>SEEK "12345" ;
>   IN Customer ;
>   ORDER CustId
>
>

>
>Both should yeild the same result (barring any
>fat finger errors on my part in the example
>above). VFP should encounter a little bit of
>overhead in determining which index to use
>(i.e. it's "strategy") but is there a minimum
>number of records that must be in the table to
>make Rushmore worth while? Is there a minimum
>number of optimizable expressions? That kinda
>thing.
>
>TIA for any feedback you guys can give me.
>
>

>
>   ...kt
>