I'm trying to delete a row from a datatable that is the datasource of a datagrid by using the following code :
table.Rows.Remove(table.Rows(selec - 1))
table.AcceptChanges()
But when I try to insert new row with the same id that had the deleted row I've an error because the deleted row still exist in the table. Why I want to delete it definitively!!!!
thank's for any help.
Erwan
definitively deleting a datarow from a datatable
Hot Topic
- loading treeview from a DataBase
- Code secured against DISSASEMBLING it.
- Change component icon
- MySQLDataAdapter Insert Not Working...
- DataGridViewComboBoxColumn and binding to a Custom Collection (BindingList<T>)
- How do I get the MSChart control into VB.NET?
- Modifing The Order of The Column Heads When Binding An Object
- Encrypt appSettings of the app.config file
- Can I display any text on RowHeaders in the DataGridView?
- Visio Drawing control won't load in 2005
Windows Forms
- passing events
- Modify setup.exe?
- Microsoft Outlook 11.0 Object Library
- Debugging a VB.NET "Windows control"
- Single Instance application - First instance crashes when second instance launched
- Clickonce vs. Updater Application Block
- Could anyone answer this client error msg? tx
- Embedded Resources And Release Builds
- Set SelectedValue ComboBox
- DataGridView with an AlternatingRowsDefaultCellStyle
definitively deleting a datarow from a datatable
jake072
2) If the table has been sorted, if you've deleted rows, or if you've filtered the data you're looking at, the index you're looking at is going to be off (it's going to be the unsorted version, with deleted rows still in it unless you've called AcceptChanges). It's simplest to bind to a DataView, like this:
Dim dv As New DataView(table)
myGrid.DataSource = dv
dv(selec - 1).Delete()
3) If you have a database where you're storing the data, you don't want to call AcceptChanges until you've sent the data back there -- Delete() marks the row as "Deleted", AcceptChanges will really get rid of the row now. (Yes, if you don't have a database, you probably do want this.) Also, if you have a database, I'd suggest you try to avoid reusing the same ID, so that you don't end up with misparented data. (As in, a new customer that gets all the orders for an old customer that's gone now.)
If you don't have a database, you won't have to use AcceptChanges any more once you change from Remove to Delete (but you can still call it if you want to).
-Scott