It's great that 1.02 solved the speed problem of SetRange.  But, for some reason, it is still very slow to use with DevEx's lookupcomboBox.  When I click the dropdown button, it takes a long
time before the dropdown list appears.  I've tried it with other DB but doesn't have this problem.   However, it may not be really a problem of EDB because I also tried other
lookupcomboBoxes (e.g. the standard Delphi one and JEDI's one) and they are fine with EDB.

The problem is that I use DevEx's components a lot for consistent look&feel.  It's quite difficult for me to drop it now.

PK

<<But, for some reason, it is still very slow to use with DevEx's lookupcomboBox.  When I click the dropdown button, it takes a long
time before the dropdown list appears. >>

I've found it.  cxLookupComboBox supports both case sensitive and case insensitive search.  It does this by calling Locate.  By default, it is case insensitive.  I found that EDB Table's Locate
is slow when loCaseInsensitive option is set.  That's the reason why it takes a long time for the dropdown list appears.

<< I've tried it with other DB but doesn't have this problem.   However, it may not be really a problem of EDB because I also tried other
lookupcomboBoxes (e.g. the standard Delphi one and JEDI's one) and they are fine with EDB.>>

The other database I tried supports very fast case insensitive Locate.  Perhaps this is a nice to have feature for the next version of EDB.   But honestly, if I really need case insensitive
search for a particular key, I would have set it to uppercase before saving the record.

PK

<< I've found it.  cxLookupComboBox supports both case sensitive and case
insensitive search.  It does this by calling Locate.  By default, it is case
insensitive.  I found that EDB Table's Locate is slow when loCaseInsensitive
option is set.  That's the reason why it takes a long time for the dropdown
list appears. >>

Do you actually have a case-insenstive index (collation = *_CI) that can be
used by the Locate for the search ?

--
Tim Young
Elevate Software
www.elevatesoft.com

<<Do you actually have a case-insenstive index (collation = *_CI) that can be
used by the Locate for the search ?>>

The index field is an integer field, so collation cannot be selected.

PK

<<Do you actually have a case-insenstive index (collation = *_CI) that can be
used by the Locate for the search ?>>

By the way, you actually pointed this out when I first reported this problem a month ago.  I didn't dig into it deep enough because I thought case sensitivity should not matter with integer
field.  Obviously my assumption was wrong.

PK

<< By the way, you actually pointed this out when I first reported this
problem a month ago. >>

Yes, unfortunately I don't usually remember things such as this without a
bit of prodding, especially if I forget to record the incident, such as was
the case here.

<< I didn't dig into it deep enough because I thought case sensitivity
should not matter with integer field.  Obviously my assumption was wrong. >>

It's the basic root of the problem - EDB expects to get a match on the
collation's case-sensitivity, even for columns that don't have collations
such as integer columns.

This should be fixed within the next week in a build 2.

--
Tim Young
Elevate Software
www.elevatesoft.com