>Geo,
>
>Is Rushmore smart enough to re-use the bitmap from your first LOCATE when it does the second LOCATE? Since you're not closing the table in between... maybe?

Dave,

I have no idea. I never even given much thought to this aspect (mainly because it's so specifically VFP rather than a VFP/Windows issue). In fact, the first set of tests that I did, didn't include the GO TOP. I would think that the value would have nothing to do with the problem, unless in the second LOCATE, it checks the current record first because the index tag is set. Ed probably knows more about this than I. I don't have an idea why this is happening, but, like Mike, thought that without having the tag set it would be faster. I'm at a loss, and will listen to any reasonable (or even unreasonable< s >) explaination anyone has to offer.