>Is LOCATE FOR going to be relatively efficient for a situation where SET KEY limits the records to, oh, a few dozen records at most? IOW, does LOCATE FOR use the SET KEY index? I have hardly ever issued a locate, since have been scarred by them in Clipper days. :-)

As you probably know, LOCATE is Rushmore-optimizable. I don't know what the effect would be with SET KEY in place, but since that requires an index, I'd expect it not to disable Rushmorization.