Re: Finding a record in a TADOTable

D Whaley wrote: 
The seek method uses the index if the table is live.

Otherwise you are actually looking at a snapshot of the data. Therefore you
do not have access to the index directly.

It would seem that a snapshot of data could also include a snapshot of any given index. Too bad it does not work that way. In my particular case I know that the ADO table will not be accessed by any other connection so having a snapshot with an index would enable me to find a record quickly in the table.

I will probably use a client data set in order to accomplish this, but my testing using a client data set shows that it is very slow applying a large number of changes to a table on the server using ApplyUpdates.

I use locate quite often and seems to work well enough on reasonable size
result sets.

Unfortunately some of the tables are very large and I need to find a record by its index in order to update it. I can use Locate but the extra time it will take to find a record will be prohibitive.


"Edward Diener" <eddielee_no_spam_here@xxxxxxxxxxxxxx> wrote in message
news:42934948$1@xxxxxxxxxxxxxxxxxxxxxxxxx

I would like to be able to find a record in a TADOTable based on an
index. The only thing I have found in this regard is the Seek method but
this appears to require a number of other properties to be set and is
supposedly supported only with a few RDBMSs. The other possibility is
the Locate/Lookup set. Is there really no way to use the indices of a
TADOTable to find a record ? It would seem natural that any table would
allow one to use an index to quickly find a record in the table, else
what purpose do indices serve.




.