>>But in this case, the initial LOCATE has a pause (it seems to be doing a rather slow search for the index, like it's considering the options, then zips to the record), and then subsequent CONTinues are instantaneous...and we're talking major table size here...well, I always use SEEKs programmatically anyway on these tables, so it's kind of moot that LOCATE may be a bit slower...
>
>OK...sounds like it is looking for an index it can use, then once it finds it, it is used on the CONT.
Yes, agreed. Hadn't considered it before, but these large lookup tables have as many as 25 or 30 tags, probably a factor...
The Anonymous Bureaucrat,
and frankly, quite content not to be
a member of either major US political party.
