Hi!

You're right, controlling index slow down the process for sure when command is not optimized.
Is SET("OPTIMIZE") = "ON"? Do you have indexes on cusID and po fields in that table? These indexes contain filter for indexing?
If answer is "YES", "YES" and "NO", LOCATE should work quickly and not depended on the controlled index because Rushmour optimization is used.


>My form using :
>
> LOCATE cusId = '123' AND po = '1234'
>
>to locate some records, it is really slow. The table is child table. I suspect the controlled index will influence the search. Because when I try the command in command window. It is very fast.
>
>Can anyone help me to solve the problem.
>
>TIA.