> Thanks Paul. I'll see if my users can live with that. If not, I

may

> have to convert this module off of IBO native components to the

bde

> replacement components.

Not a very "forward thinking" move!!
BDE is dead!
(Or at least in its dying throes. Once you truly get away from
BDE/truly get into IBO, there simply is NO looking back!)

The journey is long & steep, but the rewards are many & fruitful!

Now,
If I'm understanding what you want correctly, I have implemented
this feature throughout my app.

Set the SeekNearest property of the TIB_ComboBox to True.
Then set the 'CaseInsensitive' flag of ColumnAttributes for the
field in question of the LOOKUP dataset.
If this still doesn't work properly, try this: (I found it was due
to the case-insensitivty, on a case sensitive field)

Make a duplicate field in the lookup table, which stores only UPCASE
data of the field you want looked up.
Then when you set the CaseInsensitive flag to true, also put this
new UPCASE field in the Upper-Case Equivalent box.

Then, all you need is an Insert and an Update trigger, which sets
the UPCASE field accordingly (i.e. exactly same text as main field,
but UPPERCASE)

Example:
You have a Client table (lookup)
In this table, you have a ClientName field. Make another field
called UPNAME, which is where the upper-case names will be stored.

On, for example, your Invoice form, you have the TIB_ComboBox which
is linked to the Client table.
In the combo, set SeekNearest to True.
In the Client TIB_Query, set the ColumnAttribute for the ClientName
field to be 'CaseInsensitive', and put UPNAME in the 'Upper-Case
Equivalent' box

This works for me.

Like most things in IBO, they take a little more to conceptually
understand, but when you do it all starts making (good) sense.

Rgds,
-Ryan

Se