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

I was thinking of that, but got the impression that the SET KEY was applied for different purposes, in a different part of the program. Hence you might still want to LOCATE with a SET KEY active.