Deane
It sounds like FindKey may be better for you. I use TTable.Locate only when
I am looking for a specific, single record. Others may use it differently.
Or, you could filter the dataset and use FindFirst and FindNext to solve
this problem. This might be the easiest solution.
Richard
Ivan Detkov
Zedak Corp.
Richard A. Howard wrote in message <6l46bc$ot...@forums.borland.com>...
I also have a question about findNearest , is it possible that it's not
compatible with Interbase table, with my paradox table, it's working great
but with my interbase table, it gives me an 'Field index out of range' error
at run time. Any solutions?
Mario Paradis
CIM Inc.
Deane Hafling a écrit dans le message <35756D...@JUNO.COM>...
Will this work if it is not a key field though?
Deane
Ivan Detkov
Zedak Corp.
Deane Hafling wrote in message <3577F2...@JUNO.COM>...
Then how _do_ you do a "FindNext"???
--
David Ullrich
sig.txt not found
To move to the next record I am using
1. Locate --> No way; IMHO it is generally not good idea to use this method.
2. Filtering --> Next; It is all right for SQL Servers in simple cases.
3. FindFirst --> FindNext. It is all right for desktop databases.
With SQL Servers and big tables or complex search criteria I can recommend
only TQuery. You are going to query server every time you need filter
records. It is the only reasonable strategy in client/server architecture.
Ivan Detkov
Zedak Corp.