You are not using the properties correctly. Don't put mixed case values in a
column that is indicated to be the NOCASE equivalent column.

You either need to have only upper case text in the DEPARTMENT column or you
need to make the setting as follows:

> qrDept.ColumnAttributes contains 'DEPARTMENT=NOCASE'

By leaving it out IBO will use the UPPER( ) where appropriate. Just keep in
mind that you lose the benefit of having an index so for larger datasets
this is undesirable.

HTH,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Brian Dunstan" <bdunstan@...>
To: <ibobjects@egroups.com>
Sent: Tuesday, November 28, 2000 8:04 PM
Subject: [IBO] TIB_LookupCombo case insensitive inc search


> I think there is a problem with case insensitive searching using
> TIB_LookupCombo.
>
> Using the Samples\LookupCombo\LookupCombo.dpr sample program, I have run
> this test.
>
> 1) Using WISQL I have inserted another department record 'corp x'.
> insert into department values(
> 1,'corp x',null,105,100000,'Monterey','(408) 555-1234'
> )
>
> 2) Run LookupCombo.dpr and type what you like into the Department
> LookupCombo and you can't get to 'corp x'. The only way to select 'corp x'
> is to scroll to the end of the list and click on it.
>
> qrDept.AutoFetchAll is True
> qrDept.ColumnAttributes contains 'DEPARTMENT=NOCASE=DEPARTMENT'
>
> In a previous post a month or so ago, relating to search performance,
Jason
> said:
>
> > If you are pulling all the records to the client then there is no
> > appreciable benefit to having a dedicated column for the uppercase
> > equivalent. IBO will perform it in memory as you expect.
>
> So I think this is SUPPOSED to work, but it looks to me like it doesn't.
>
> Am I just being a duffer (again) or is there really a bug here :-)
>
> Any help in getting expected performance from this ubiquitous control
would
> be much appreciated :-)
>
> TIA,
>
> Brian
>
>
>
>