hello,
can someone confirm this:
the delphi Locate method does not use available indices (and therefore slows down finding a record significantly).
i was using the 2.22 series of edb before and this problem did not exist.
the corresponding sql-statement in the edb manager ist fast

Gruetzmacher

>can someone confirm this:
>the delphi Locate method does not use available indices (and therefore slows down finding a record significantly).
>i was using the 2.22 series of edb before and this problem did not exist.
>the corresponding sql-statement in the edb manager ist fast

It should do and fall back to using brute force when an index doesn't exist. I have an incident which I'm talking to Tim about via email that may be related - I "think" I've tracked it down to a difference in behaviour with FindKey & Locate between 2.22 and 2.23. I'm still trying to produce a test case.

Roy Lambert

Hendrik,

<< the delphi Locate method does not use available indices (and therefore slows down finding a record significantly).
i was using the 2.22 series of edb before and this problem did not exist. the corresponding sql-statement in the edb manager ist fast >>

Please email me your database catalog, relevant table files, and the example table/query that is exhibiting the issue along with the Locate call that you're using, and I'll take a look.

And no, this isn't the same issue as Roy's.

Tim Young
Elevate Software
www.elevatesoft.com

just to clarify:
the problem was not related to edb at all but rather the amount of data that has build up within 2 years. in fact the index was never used at all but locate could easily be modified to use it.
everything is fine