i have a vb.net winforms application. i have one particular form which has fields bound to a datasource and uses a bindingsourcenavigator. there is also a "save" button to save changes to any particular record.
when i run this application, i can hit the save button and my changes are saved just fine. when my users in another state hit the save button it works SOMETIMES.
i can turn sql server trace on and watch as i hit the save button and see the update called. but when my users hit the save button......no sql server activity occurs.
my users and i are both hitting a remote sql server.
what in the world could cause this issue?
it's the same code
hitting the same sql server database
the only thing i can think is that maybe either the datatable...or the bindingsource....or the bindingsourcenavigator.....is not registering that the data is dirty.
but it does for me!
so why not them?
i just can't explain it
here is my update sub:
Private Sub saveData()
Me.Validate()
Me.TblMyTableBindingSource.EndEdit()
Me.TableAdapterManager.UpdateAll(Me.DsMyDataset)
End Sub
this runs and generates no errors.....
BUT.....
the sql server update never fires!
when i run this application, i can hit the save button and my changes are saved just fine. when my users in another state hit the save button it works SOMETIMES.
i can turn sql server trace on and watch as i hit the save button and see the update called. but when my users hit the save button......no sql server activity occurs.
my users and i are both hitting a remote sql server.
what in the world could cause this issue?
it's the same code
hitting the same sql server database
the only thing i can think is that maybe either the datatable...or the bindingsource....or the bindingsourcenavigator.....is not registering that the data is dirty.
but it does for me!
so why not them?
i just can't explain it

here is my update sub:
Private Sub saveData()
Me.Validate()
Me.TblMyTableBindingSource.EndEdit()
Me.TableAdapterManager.UpdateAll(Me.DsMyDataset)
End Sub
this runs and generates no errors.....
BUT.....
the sql server update never fires!
Last edited: