Combobox showing first item??

[Nate]

I have used the feedback on this issue to remedy my comboboxes showing
the first item on the list when a new record is added to the binding
context ---
Me.BindingConte xt(dsOrders, "tblOrders").Ad dNew()
Me.ComboBox1.Se lectedIndex = -1

but... how do we deal with the same issue during record navigation?
When I move forward or backward onto a null field the combo defaults to
the first item on the list again?

Me.BindingConte xt(dsOrders, "tblOrders").Po sition =
(Me.BindingCont ext(dsOrders, "tblOrders").Po sition + 1)

I am convinced that anyone using combos is having this problem...

I am binding early, clearing and rebinding late, trying many variations
to no avail. I have added an empty string value to the first item of
all my combos - this displays an empty box for null fields, but is not
optimal. Anybody have a workaround for this??

[ng]

I prefer an unbound combobox.

Tom

Nate wrote:

I have used the feedback on this issue to remedy my comboboxes showing
the first item on the list when a new record is added to the binding
context ---
Me.BindingCont ext(dsOrders, "tblOrders").Ad dNew()
Me.ComboBox1.S electedIndex = -1

but... how do we deal with the same issue during record navigation?
When I move forward or backward onto a null field the combo defaults to
the first item on the list again?

Me.BindingCont ext(dsOrders, "tblOrders").Po sition =
(Me.BindingCon text(dsOrders, "tblOrders").Po sition + 1)

I am convinced that anyone using combos is having this problem...

I am binding early, clearing and rebinding late, trying many variations
to no avail. I have added an empty string value to the first item of
all my combos - this displays an empty box for null fields, but is not
optimal. Anybody have a workaround for this??

[Bart Mermuys]

Hi,

"Nate" <na************ ***@hitchcock.o rg> wrote in message
news:11******** **************@ f14g2000cwb.goo glegroups.com.. .

I have used the feedback on this issue to remedy my comboboxes showing
the first item on the list when a new record is added to the binding
context ---
Me.BindingConte xt(dsOrders, "tblOrders").Ad dNew()
Me.ComboBox1.Se lectedIndex = -1

but... how do we deal with the same issue during record navigation?
When I move forward or backward onto a null field the combo defaults to
the first item on the list again?
I recently posted a workaround for what i can only guess deals with your
problem. Are you talking about lookup ComboBox's to which you have added a
binding for SelectedValue ?,eg.:

Me.ComboBox1.Bi ndings.Add( "SelectedValue" , dsOrders,
"tblOrders.Some FkField" )

If so, then yes there is a problem with null values, and here is a
workaround:

AddHandler Me.BindingConte xt(dsOrders, "tblOrders").Po sitionChanged, _
AddressOf CmPositionChang ed

Private Sub CmPositionChang ed( ByVal sender As Object, ByVal e As
System.EventArg s)
'
Dim cm As CurrencyManager = _
DirectCast(send er, CurrencyManager )
Dim lv As DataRowView = _
DirectCast(cm.C urrent, DataRowView)
Dim cb As ComboBox

For Each bnd As Binding In cm.Bindings
If (bnd.PropertyNa me = "SelectedValue" ) And _
(TypeOf (bnd.Control) Is ComboBox) Then
cb = DirectCast(bnd. Control, ComboBox)
If (lv(bnd.Binding MemberInfo.Bind ingField) Is DBNull.Value) And _
(cb.SelectedInd ex <> -1) Then
cb.SelectedInde x = -1
End If
End If
Next
End Sub
HTH,
Greetings

Me.BindingConte xt(dsOrders, "tblOrders").Po sition =
(Me.BindingCont ext(dsOrders, "tblOrders").Po sition + 1)

I am convinced that anyone using combos is having this problem...

I am binding early, clearing and rebinding late, trying many variations
to no avail. I have added an empty string value to the first item of
all my combos - this displays an empty box for null fields, but is not
optimal. Anybody have a workaround for this??