Bruce,

>One thing I've found is that for the first optimizable LOCATE issued, on a table with many (20 or 30) tags, there sometimes is a distinct pause while vfp has to find the correct one. Subsequent LOCATE or CONTINUE are about as fast as SEEK after that...same thing, of course, with SQL...

>But that alone can be a reason to use SEEK instead of LOCATE (and even SQL where applicable), since order is already applied.

You might be right. All rushmore optimizable commands have to search for the right index (or indices) to optimize whereas SEEK uses the right index rightaway.

walter,