Hi Team,
I am obviously doing something wrong here..
EDBTable, VARCHAR field 'Name'.
EDBTable.Filter = Name like 'roy%'
FilterOptions|foCaseInsensitive is False.
When I set Filtered to True I get all records starting with 'Roy', not 'roy' as wanted.
The field Name has an index however it isn't flagged as case-insensitive.
It doesn't matter what the setting of FilterOptions|foCaseInsensitive  is I get the same result.

Thoughts/suggestions appreciated.

Regards,
Ian

Ian

I have all my VARCHAR fields set to case insensitive so this is a guess

Filters such as LIKE are an ElevateDB extension and since you have an index defined that is being used and the foCaseInsensitive is being ignored.

You can try

_Name collate ansi_ci like 'roy%'

but that will not use the index.

The best recommendation, unless you need case sensitivity is to set all VARCHARs and CHARs to case insensitive. It does affect sorting, (ie roy and ROY will be sorted together) but in a way that more users seem to expect.

Roy Lambert

Hi Roy,
Thanks for the info.

Roy Lambert wrote:

Filters such as LIKE are an ElevateDB extension and since you have an index defined that is being used and the foCaseInsensitive is being ignored.

IB - Oh.  I didn't consider/realize that.  Hmmm.  Have to rethink some things.

The best recommendation, unless you need case sensitivity is to set all VARCHARs and CHARs to case insensitive. It does affect sorting, (ie roy and ROY will be sorted together) but in a way that more users seem to expect.

IB - As it turns out this particular Customer prefers case insensitive searches so it turned out OK.  Having said that I would still like the option to work.  Sigh.

Regards,
Ian

Ian


Report it to Tim - see what he says.

Roy Lambert