BindingNavigatorAddNewItem Goes to existing record?

Answered BindingNavigatorAddNewItem Goes to existing record?

  • Tuesday, February 28, 2012 7:24 PM
     
     

    When I click the wizard created BindingNavigatorAddNewItem button my form goes to an existing record instead of what I would expect, which is to display an empty record that the user can populate.

    Update is working OK.

    I'm using bound controls dropped on form from the DataSource - Dataset.

    The Dataset has more than one table w/o any relationships (shouldn't matter but...) The table being updated as a computed identity column.

    I'm a Newbe with bound forms in VS2010 VB.Net Windows Forms and the Wizard generated datasets et al. I usually use ADO.Net to do things but thought I would try the bound controls - marginal luck so far.

    Did I miss something that allows the wizard to add a new record?

All Replies

  • Tuesday, February 28, 2012 10:36 PM
     
     Answered

    Hello Bob Heitzman,

    When I click the wizard created BindingNavigatorAddNewItem button my form goes to an existing record instead of what I would expect, which is to display an empty record that the user can populate.

    Update is working OK.

    I'm using bound controls dropped on form from the DataSource - Dataset.

    The Dataset has more than one table w/o any relationships (shouldn't matter but...) The table being updated as a computed identity column.

    I'm a Newbe with bound forms in VS2010 VB.Net Windows Forms and the Wizard generated datasets et al. I usually use ADO.Net to do things but thought I would try the bound controls - marginal luck so far.

    Did I miss something that allows the wizard to add a new record?

    the BindingNavigatorAddNewItem must add a new record, do not see an existing one, and very strange, try re-running a new wizard in the dataset by first removing all references to designers and code of the old dataset.

    Regards.


    • Marked As Answer by Bob Heitzman Wednesday, February 29, 2012 4:08 PM
    •  
  • Wednesday, February 29, 2012 4:08 PM
     
     

    I suppose your suggestion may work but I've had zero luck trying to repair wizard generated code and dataset. I just have to start over once the form is corrupted. I looked at these features way back an abandoned them and I'm glad I did given my recent experince trying to use them again.

    Hopefully the next generation won't be so fragile.