In my client Windows application, I am receiving a DataSet containing one 
DataTable.  This comes to my client via the business tier on a different 
physical machine (we're using WCF if that matters).

After I make changes to the data in the underlying DataTable, I send the 
DataSet back to the business tier.  In the business tier, what should my 
code look like to persist the data up to the database?

I'm assuming I need to do something like this:

Dim Connection As New SqlConnection()
Connection.ConnectionString = My.Settings.COWFeedyardConnectionString
Dim Command As New SqlCommand()
Command.Connection = Connection
Dim DataAdapter As New SqlDataAdapter()
DataAdapter.UpdateCommand = Command
DataAdapter.Update(PenDataSet)

... but I get the errror: "Update unable to find TableMapping['Table'] or 
DataTable 'Table'."

Thanks for any help,
Ron

And actually, I just changed the update line to instead read:

DataAdapter.Update(PenDataSet, "Results")
The code now does not break on error, it seems to execute the line but no 
changes were actually ssaved to the database.

Thanks,
Ron




"Ronald S. Cook"  wrote in message 
news:ew48a1lxHHA.3956@TK2MSFTNGP06.phx.gbl...

> In my client Windows application, I am receiving a DataSet containing one 
> DataTable.  This comes to my client via the business tier on a different 
> physical machine (we're using WCF if that matters).
>
> After I make changes to the data in the underlying DataTable, I send the 
> DataSet back to the business tier.  In the business tier, what should my 
> code look like to persist the data up to the database?
>
> I'm assuming I need to do something like this:
>
> Dim Connection As New SqlConnection()
> Connection.ConnectionString = My.Settings.COWFeedyardConnectionString
> Dim Command As New SqlCommand()
> Command.Connection = Connection
> Dim DataAdapter As New SqlDataAdapter()
> DataAdapter.UpdateCommand = Command
> DataAdapter.Update(PenDataSet)
>
> .. but I get the errror: "Update unable to find TableMapping['Table'] or 
> DataTable 'Table'."
>
> Thanks for any help,
> Ron
>
>