Jim,

I wonder if you could offer a little more reasoning for this one than simply 'locate is optimizeable while GO TOP / GO BOTTOM are not'??

The reason should be obvious - ZERO optimization required for the two special cases GO TOP and GO BOTTOM, whereas LOCATE would seem to NEED optimization EVERY time.

Just because GO TOP and GO BOTTOM are not optimizeable should *not* immediately lead to the conclusion that they are *not* "optimized" within VFP. And even if not specifically "optimized", their very destinations should lead to an immedaite answer which is the final answer, and not some intermediate answer.

Regards,
Jim N

>>John, if you re-set the record pointer (GO TOP, etc.) after the SET DELETED command it will take effect in the INIT as well.
>>
>>Barbara
>Barbara,
>
>Actually LOCATE is faster than GO TOP in certain situations. It is because LOCATE is optimizable while GO TOP and GO BOTTOM are not.