>Hi.
>
>I have a product table with 6000 records. I'm using txtquickfill in a form to pick up a product code. It works fine, in my local developer machine. Once I ported this to the client network, it got really slow. I have an index for the product code field and one for the product name.
>With the code, is lightning fast, but with the name, turtle slow.
>The only difference between them is that the code's length is character 15, and the name 60.
>Saw that Dave uses "locate for" to search for a match. I have tried to set the lExactCase to .T. , index on UPPER(code_name). Before I set lExactCase to .T. , the search on the Code was slow as well, as the code wasn't indexed on UPPER.

I don't know whether I should answer this question because the deliveryman just arrived with a small parcel from Brazil. My German Shepherd dog sniffed the box and got very excited - he doesn't get excited about music? I'm almost too frightened to open it <s>. I will open it after I have pushed the Send button <bg>.

Back to this. Are you sure that the index on the NAME column is actually being used? What happens if you put the products table (the lookup table) on the local workstation -- I presume that is on a network drive at the moment? Also, even if you replace LOCATE FOR with a SEEK, I don't think you will find much of a difference. A Rushmore optimized LOCATE FOR, I am pretty sure uses an implicit SEEK, internally.

These suggestions assume that you have the properties set correctly in the control. Let me know.

Best