bug in 3.2.0.1

[Christian Pogea]

i moved from syncfusion 2.0.5.0 to 3.2.0.1 and get this exception after open a mdi client with a databoud grid.

Informationen über das Aufrufen von JIT-Debuggen
finden Sie am Ende dieser Meldung, anstatt in diesem Dialogfeld.

************** Ausnametext **************
System.ArgumentException: Konnte nicht an den neuen ValueMember gebunden werden.
Parametername: value
at System.Windows.Forms.ListControl.set_ValueMember(String value)
at Syncfusion.Windows.Forms.Grid.GridComboBoxCellModel.FillWithChoices(ListBox listBox, GridStyleInfo style, Boolean& exclusive)
at Syncfusion.Windows.Forms.Grid.GridComboBoxCellRenderer.OnInitialize(Int32 rowIndex, Int32 colIndex)
at Syncfusion.Windows.Forms.Grid.GridCellRendererBase.Initialize(Int32 rowIndex, Int32 colIndex)
at Syncfusion.Windows.Forms.Grid.GridCurrentCell.Refresh()
at Syncfusion.Windows.Forms.Grid.GridDataBoundGrid.OnEnter(EventArgs e)
at Syncfusion.Windows.Forms.ScrollControl.wiredParentForm_Enter(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnEnter(EventArgs e)
at System.Windows.Forms.Control.NotifyEnter()
at System.Windows.Forms.ContainerControl.UpdateFocusedControl()

[Administrator]

It appears that the databinding cannot find the value member it is looking for. Can you provide more information? Has the DataSource/DisplayMember/ValueMember been set up for this column by the time you try to enter the grid? Is that datasource properly initialized at this point? Can you upload a sample showing this problem?

[Christian Pogea]

the valuemember of a combobox column seems to be case sensitive now :-(

the whole dataset ist not case sensitive so why is your combobox column casesensitive???

[Administrator]

Our binding support includes support for strongly typed objects using property descriptors which are case sensitive. We do not make a distinction between dataset binding and typed object binding. That is why our implementation is case sensitive.