Hi,

The combo does not know anything about the back end, it only knows about the DataType of the field you are binding to. So if both the column on the list and the values you are binding to are the same type, it should work.

Just to be sure, I tested this out using Integer (which I am sure work, since this is what most people use for the ValueMember) and then I tested it with Byte, just in case Byte behaves oddly for some reason. They both work perfectly fine for me and the ItemNotInList event never fires when I pick an item from the list.

I also tested this using both UltraCombo and UltraComboEditor and they both work the same.

I'm attaching my sample here so you can see if it gives you the same results.

I have updated my procedure to explicitly convert the identity tinyint field to tinyint and it now comes into the DataTable as Byte. However, my combo problem still exists: selecting a new value fires the NotInListEvent though the proposed value in the event is correct and the dataset is updated correctly. Again, if then selecting the original value (which matches the bound field existing value) the event is not fired. To reproduce, I would populate a combo with a DataTable with a byte DataValue and string DataMember and bind the combo to a Byte column in the record datasource. The Combo works fine with int DataTypes. Thanks.

Upon further research, I have found the following: apparently there is a MS "confirmed bug" on tinyint datatypes when they are also identity columns. The datatype is property assigned as Byte in the NET DataTable when not identity, but as int32 when indentity. This presumably is causing my problem as the field is an identity column.

Yes, 2010.2. The combo control is being bound to a tinyint field of the dataset (or System.Byte in the typed dataset DataTable. The combo datasource is a datatable of the underlying lookup values, also tinyint in SQL or Byte in the datatable. Other combos bound to ints are working fine, it is only this one which throws the NotInList and only when selecting a value that is not the current value of the bound field. I will have to check on how the lookup values are being returned to the normal dataset, as bytes or other. thanks.

Okay, sorry, I assumed it was a grid.

But anyway, this should work fine as long as you are sure that the Value of the control is being set to a Byte and also the DataValues of the items on the list are also Bytes.

I know that this works with other data types, so there's no reason why Bytes should be any different.

sunibla said:

Version 2110.2

Ummm... there is no such version. I assume this is a typo and you mean 2010.2?