>>
>>Why don't you use SEEK ? You will only need to index the view on cID...
>>
>>seek this.value
>>
>>BOb
>
> Well, it kept giving me a "Table has no index order set" error - and LOCATE didn't ;-). According to the help, LOCATE should do a Rushmore optimization on it anyways (and it's a small file). Those were the only >real< reasons I didn't.

If the cursor only has 90 records, the LOCATE should not be taking that long, optimized or not. Have you stepped through the code to make sure that your LOCATE statement is what is taking so much time? I know stepping through the code is a daunting task with codebook, but it should point out what is really taking so mush time. you could also run the code through the coverage logger and check out the listing to see what routines are stalling everything up. To summarize, it doesn't sound to me like an optimization issue.