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

I see your dog has good taste for music. Mine thinks only of food, and she's got only one tooth !!!


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

Well, as usual, the computer mistake ... not mine, of course. Clients usually believe this. The index for the name was compound ... for some reason that only God knows, it was name+code , maybe I thought some 5 years ago, when I designed this system, that they could have two products with the same name and different codes ... anyway, create the index for the name with the name field exclusively. I'm happy now.

Once we are on the subject of indexes, do you create the Deleted() for all tables ? I've read different opinions about this. I haven't done so, but was thinking if this would make it even faster.

Obrigado.