>All of this is speculation, but its just not that simple. Determining which index tag to use shouldn't account for that much delay. I only had one index in my little test program. The number of records is what caused the delay. Rushmore (in the LOCATE) is paving the way for a probable CONTINUE. Rushmore is paving the way for quick access of the records that meet the condition. This involves recording a list of records that met the condition and that would account for the delay increase with the number of records.

Well, I want to believe you, but since I am hard to convince, i must see it with my own eyes.

>I should probably now refer you to Foxpro Advisor September 1996, and my own article in Foxpro Advisor July 1997. These articles operate on the premise that Rushmore is doing a lot more than a seek does.

Sadly, I don't have access to the articles, so It would be hard to read the articles.

>Regardless, the point is that seek is way faster than locate in simple tests because the two search techniques are vastly different. There should not be any question which to use. Seek is for finding a single record, locate/continue and SQL are for finding a set of records.

Yep, I fully agree. B.T.W. I Don't use seek as often is I use LOCATE because mostly I use SET RELATION to look up records where it can be applied


Walter,