Subject | Re: [IBO] IB_combobox.autodropdownproperties?/UndataboundIB_combobox |
---|---|
Author | Helen Borrie |
Post date | 2003-07-11T07:42:25Z |
At 07:03 AM 11/07/2003 +0000, you wrote:
IB_Combobox". The crucial word here is "searching". What is it searching?
The way you'd normally the ib_combobox is this:
In the Items property, load the "human-readable" strings, e.g. your SINGLE,
MARRIED, DIVORCE, SEPARATED, WIDOW
In the ItemValues property, load the "key" values, e.g. your S, M, D, SE,
W, so that the indexes of the two stringlists map correctly.
Point the Datasource property of the ib_combobox to the ib_datasource of
the [parent] query that needs to use the values. Then for the Datafield
property, select the value from the parent query's fieldlist. So, let's
say that the parent query has a column "MaritalStatus" which can take one
value from the set ['S', 'M', 'D', 'SE', 'W']. The Datafield property of
the combobox would be 'MaritalStatus".
The ib_combobox ITSELF is not attached to a datasource. It only POINTS TO
the datasource of the parent query.
that Items and ItemValues are the other way around - you put the "key"
values in ItemValues, and the strings that the user sees are in Items.
Did you get confused because you thought ib_combobox was
"double-data-bound", like IB_LookupCombo? It's not. The dropdown list of
TIB_Combobox is not attached to a data object. That's what I was trying to
tell you, back at the original response. TIB_ComboBox and TIB_LookupCombo
are quite different from each other. They don't even share a common ancestry.
Helen
>I would like to use it for searching for example I drop a IB_comboboxIt's not clear what you mean by "my GUI will provide a searching thru this
>which as itemvalues and items property then I will fill up those
>itemvalues and items property for example ... I will be the following
>for the items property ... SINGLE, MARRIED, DIVORCE, SEPERATED, WIDOW
>and in the itemvalues property (I will have S, M, D, SE, W. Then my
>GUI will provided a searching thru this IB_combobox... So everytime
>when the IB_combobox will trigger the on change the query will
>adjust to the request of the user? and I think this setup up will not
>require the datasource property of the IB_combobox to be set.
IB_Combobox". The crucial word here is "searching". What is it searching?
The way you'd normally the ib_combobox is this:
In the Items property, load the "human-readable" strings, e.g. your SINGLE,
MARRIED, DIVORCE, SEPARATED, WIDOW
In the ItemValues property, load the "key" values, e.g. your S, M, D, SE,
W, so that the indexes of the two stringlists map correctly.
Point the Datasource property of the ib_combobox to the ib_datasource of
the [parent] query that needs to use the values. Then for the Datafield
property, select the value from the parent query's fieldlist. So, let's
say that the parent query has a column "MaritalStatus" which can take one
value from the set ['S', 'M', 'D', 'SE', 'W']. The Datafield property of
the combobox would be 'MaritalStatus".
The ib_combobox ITSELF is not attached to a datasource. It only POINTS TO
the datasource of the parent query.
>The reason I like to use the IB_combobox because the normal comboboxThen you *do* want to use the ib_combobox the way it was designed (except
>does only have items property only and no itemvalues property. I can
>also put S,M,D,SE,W in the combobox.items property but that could be
>not quite understandable for the user. But if the put SINGLE,
>MARRIED, DIVORCE, SEPERATED, WIDOW on the combobox.items values the
>searching would fail because what actually is in the data is only the
>S,M,D,SE,W.
that Items and ItemValues are the other way around - you put the "key"
values in ItemValues, and the strings that the user sees are in Items.
Did you get confused because you thought ib_combobox was
"double-data-bound", like IB_LookupCombo? It's not. The dropdown list of
TIB_Combobox is not attached to a data object. That's what I was trying to
tell you, back at the original response. TIB_ComboBox and TIB_LookupCombo
are quite different from each other. They don't even share a common ancestry.
Helen