>
>I think Mike hit on the LOCATE delay -- it's not long enough to build an index on a large table (and where the index definitely exists), just a one or two second pause...

It could be that for a LOCATE, that if an index is not found that it just does a sequential search. I know that in a SQL SELECT, Rushmore will sometimes build an index and sometimes not...it tries to figure out if it needs one.