>>Bottom line, IMHO, don't rely on undocumented features.
>..and sometimes you can't rely on the documented features either.
>
>Re: Locate vs. GO TOP and "tricks"
> I agree. According to design, use Locate when you can't use Seek because the criteria field isn't indexed. Also GO is for navigating to an absolute record number [or Top|Bottom] These concepts are very xBase to begin with. When you further limit the test by saying the table has to have a filter on it for locate to be faster, it's using an even more xbase mentality. (xbase is fine, but for extremely large tables, where it matters to measure 1.9s v. 1.1s, shouldn't SQL concepts be applied?)
>
> Write solid code and if performance is a problem, take direction from Microsoft; simply require the client also make a hardware-upgrade investment. ("waddya mean i can't run Windows2000 on my 486/66, it's got 16M of RAM")


I agree, SQL concepts SHOULD BE applied. But when you've got 200-300K lines of existing code, unless the performance is really a problem, or it flat just doesn't give you the correct results, you leave it alone. If it ain't broke...