Perhaps, it’s true 🙂 (and hopefully just momentary…)

I have LOST MY MIND!

this works just fine:

Dim conn As SqlClient.SqlConnection = New SqlClient.SqlConnection(“server=myserver;Trusted_Connection=True;Database=pubs”)

Dim cmd As SqlClient.SqlCommand = New SqlClient.SqlCommand(“select * from authors”, conn)

Dim da As New SqlDataAdapter(cmd)

Dim ds As New DataSet

da.Fill(ds)

Dim ds2 As New DataSet

Dim t As DataTable = ds.Tables(0).Copy

ds2.Tables.Add(t)

what happened to the “DataTable belongs to another dataset“ exception? Was it only in 1.0 and I just never tried it again with 1.1? I know I struggled with this forever a long time ago.

oh do I need a vacation.

Rather than just searching for workarounds or whining about this problem in my blog, I have submitted a suggestion in the Product Feedback Center. If you think this will help you, go vote on it. If you think this is a stupid idea, go vote on it.

In preparation for the ADO.NET 2.0 talk I am doing at ASP Connections in March, I am now looking at ADO.NET 2.0 from the perspective of a web developer and how some of these features will specifically enhance web development. It’s an interesting way to look at it since every type of database programming with .NET benefits from these changes.

http://www.AcehAid.org

I have written before about the wonderful new parameter of the DataView.ToTable method – DistinctRows.

Interestingly, the new DataTable that is created still has ties to the parent DataSet. So if you want to add it to another DataSet you will have to use the DataTable.Copy, rather than the new DataTable, itself.

http://www.AcehAid.org

(I have modified this post)

When you move a DataTable’s guts into another via DataTableReader, DataTable.CreateDataReader and DataTable.Load in ADO.NET 2.0, you don’t carry over the DataSet parent hook and therefore you can add this 2nd DataTable to another DataSet without having to worry about using Copy. Just a little itty bitty thing.

http://www.AcehAid.org