>>Except that since it's Rushmore-optimizable, very handy when you need to search based on multiple criteria.
>>
>
>I know it's Rushmore optimizable. My point was more that it is record based, not set based, which went out about 20 years ago.

The tables still have records, AFAIK. The "get a set of records for whatever you need" sounds like "hammer is the only tool you'll need" being recommended while you still have lots of nuts and screws.

Some scenarios come to mind - like using a locate without clauses to get to the top record under current index, or when looking for a particular record in another cursor, when the conditions are built on the fly and doing yet another SQL for just checking for existence of a particular record isn't worth the hassle (naming the cursor, having fox build buffers for it, invent a name for it, close it on exit etc etc).

So I'd rather have that screwdriver in my toolset, no matter how sophisticated the hammer.