I've tried to move to always using a SELECT. Why? SEEKs don't work when you go to a client/server environment. While you may now say "I have all DBFs", that doesn't mean that the same application won't need to move to C/S in the future. Using SEEKs will make that move more difficult. If you fully optimize the query, a SELECT will be pretty fast.


>Rather than work out data type conversions and consistent expression lengths, I sometimes like to bypass a SEEK by using a combination of a SQL Select command that is followed immediately by a check of the _TALLY.
>
>I've selected into cursors, tables, and arrays and haven't necessarily figured out which one is best. Once it's written, the SEEK is certainly much faster to execute. The later approach helps me to deal with cases where _TALLY =0, _TALLY = 1, and _TALLY > 1 in a different manner.
>
>What ideas are out there on this issue including the fastest way to do the SELECT and _TALLY? I've faced this issue in the past and I'm facing it in work I'm doing right now.
>
>Thank you in advance.