>No lectures about views, please.
>
ROFL!

>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. :-)

Since LOCATE is optimizable it shouldn't matter about the SET KEY if your LOCATE statement includes the SET KEY condition
Let's say Customer is indexed on CustKey and you want a "Fred" who lives in NY

LOCATE FOR CustKey="FRED" AND State= "NY"
will be blindingly fast if there are few "Freds" in NY.
HTH