Note that this will remove the row from the collection, and it will not
be processed if passed to a data adapter.
If you want the effect of marking the row for delete and having the data
adapter deleting the row in the underlying data source, then you should call
the Delete method on the DataRow itself.
Note that this will remove the row from the collection, and it will not
be processed if passed to a data adapter.
>
If you want the effect of marking the row for delete and having the data
adapter deleting the row in the underlying data source, then you should call
the Delete method on the DataRow itself.
>
>
--
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard. caspershouse.co m
>
"Family Tree Mike" <FamilyTreeMike @discussions.mi crosoft.comwrot e in
message news:14A3B2CB-390B-4F75-8BC8-B5028D007207@mi crosoft.com...
"Jacek Jurkowski" wrote:
Release row from a table?
>
DataRow row = Table.Rows[0].Copy? Clone?
Table.Rows.Remo ve(Table.Rows[0]) or Table.Rows.Remo veAt(0)?
>
>
Good point. I wasn't even sure if I had the question interpreted correctly
though...
I have only ever itterated over the items in a row, and stored them to a row
in the other table that was created there. The chances of two tables being
identical is remote, so the matching up of fields would be done by your code.
"Jacek Jurkowski" wrote:
The problem is that with Remove() row looses its data ...
I want to get a row (with data) from one table and add
it into another table ...
>
"Family Tree Mike" <FamilyTreeMike @discussions.mi crosoft.comwrot e in
message news:14A3B2CB-390B-4F75-8BC8-B5028D007207@mi crosoft.com...
"Jacek Jurkowski" wrote:
Release row from a table?
>
DataRow row = Table.Rows[0].Copy? Clone?
Table.Rows.Remo ve(Table.Rows[0]) or Table.Rows.Remo veAt(0)?
Comment