Thanks guys for the help and information. I changed the combobox to a
lookupcombo and got it to work. I found another problem that I had
with existing lookupcombos where the user could not type anything, he
could only drop down and select something (the users never
complained). Once I set the ordering links that problem went away.
I'll stick with the native components - no "backward thinking" for
me.

Stan

--- In IBObjects@yahoogroups.com, Paul Vinkenoog <paul@v...> wrote:
> Hi Ryan,
>
> >> 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!
> > (...)
> > 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.
>
> I think you mean TIB_LookupCombo. Stan is using a TIB_ComboBox here,
> which is basically a data-aware straight ComboBox. You supply the
> items yourself (possible loading them from a Cursor) and whatever
the
> user selects becomes the field value, and vice versa.
> It doesn't have SeekNearest and knows nothing of Lookup sets.
>
> TIB_LookupCombo comes with a complete TIB_CustomGrid as a dropdown
> list, is lookup-aware, etc. etc. It's a real heavyweight and
therefore
> also slower, and in order for it to function you have to keep a
lookup
> query open all the time.
>
> Having said all that, maybe it would be a good alternative for Stan.
> It all depends on what he uses it for.
>
>
> Greetings,
> Paul Vinkenoog