I've googled this some more and discovered it is a bug in .net 1.1 (fixed in
2.0)
I've tried a work-around to force the insert (listed on a google post):
ds.Tables(e.Row .Table.TableNam e).Rows.Add(e.R ow.ItemArray)
But this yeilds 0 rows in the ds.
If i look at the e.row.itemArray in the command window - I get a row
populated with expected values:
? e.Row.ItemArray
{Length=3}
(0): {System.Guid}
(1): {System.Guid}
(2): #1/1/2006#
But when I run the code to add the row to the DS in the immediate window I
get the following:
ds.Tables(e.Row .Table.TableNam e).Rows.Add(e.R ow.ItemArray)
Referenced object has a value of 'Nothing'.
Please note that the 'ds' is declared as follows: "Dim ds as new dataset"
Is there a solution to this? Do I build a custom datarow by hand and pass
it to my ds? Does everybody just avoid using the rowchanged event for
updating the backend in ADO.NET 1.1 ?.........????
stro" <as***@mnrr.com > wrote in message
news:gA******** *********@torna do.rdc-kc.rr.com...
I am trapping the rowchanged event on a table. I have the following code:
If e.Action = DataRowAction.A dd Then
ds.Merge(CType( sender, DataTable).Sele ct("", "",
System.Data.Dat aViewRowState.A dded))
The funny thing is - the merge operation captures No rows.
This appears to be a big contradiction.. ......
Any idea why this is happening?