VB & ADO.Net - Problems adding data

[deltamaxx]

Hello!

I'm just trying to add a new row of data to a dataset, but whenever the form is closed, it loses the data.

...

Case "Add"

TgtRw = ElementsDataSet.Tables("Elements").NewRow()
TgtRw("EID") = Guid.NewGuid
TgtRw("AL_ID") = Key
TgtRw("EType") = "R"
ElementsDataSet.Tables("Elements").Rows.Add(TgtRw)
ElementsDataSet.Tables("Elements").AcceptChanges()

End Select

ElementsDataSet.AcceptChanges()

End Sub

The form contains a gridview which is linked to the dataset, but not used for editing the data.
While the form is open, the new datarows are visible in the gridview. Everything works fine until the form is closed - reopened, the tables are empty.

btw: VS 2005; SQLExpress

Can anyone help?
Thanks!

[nateraaaa]

After you change the dataset are you inserting the data into your database? If AcceptChanges is successful you should then insert the row into your database. Then when you close and reopen the form (populating the data in the page when it opens) the data that was added should be in the form because it was added to your database.

Nathan

[deltamaxx]

After you change the dataset are you inserting the data into your database? If AcceptChanges is successful you should then insert the row into your database. Then when you close and reopen the form (populating the data in the page when it opens) the data that was added should be in the form because it was added to your database.

Nathan

Hello Nathan!

I learned that I have to update the database with the changes, so I tried this before leaving the sub:

Try

ElementsTableAdapter.Update(ElementsDataSet.elemen ts)

Catch ex As Exception

MsgBox("Update failed")

End Try

But any changes to the dataset are still not send to the database.

When I reopen the form the data added direktly to database (via server explorer) is shown normally - so the query seems to work - but the changes not.

I really have no idea ...

Thanks for your help.

Stefan

[nateraaaa]

[font=Verdana][size=2]If you are adding new data to the database you would need to call an insert stored procedure. If you are updating a current record you would call and update stored procedure. I would call an insert stored procedure after your AcceptChanges method in your "Add" case. Give this a try and let us know how it works for you.[/size][/font]
[font=Verdana][size=2][/size][/font]
[font=Verdana][size=2]Nathan[/size][/font]

[deltamaxx]

[font=Verdana][size=2]If you are adding new data to the database you would need to call an insert stored procedure. If you are updating a current record you would call and update stored procedure. I would call an insert stored procedure after your AcceptChanges method in your "Add" case. Give this a try and let us know how it works for you.[/size][/font]
[font=Verdana][size=2][/size][/font]
[font=Verdana][size=2]Nathan[/size][/font]

I've got it! - you gave me the right hint !

- The update-command of the table-adapter automatically uses the right SQL-statement according to the state-property of the rows
- the "acceptchanges"-command resets the state-propeties of the added rows so that the update doesn't identify the new rows to be send to the server ...

-> so I left out the AcceptChanges-command and everything seems to work well


Thanks for the help!

Stefan