Using it from one project, it fails just as you note. I've used the My Sql Data Adapter which works similar.
For the latest documentation on Visual Studio 2017, see Save data back to the database on docs. If you modify that data, it's a good practice to save those changes back to the database.
When an application calls the Update method, the Data Adapter examines the Row State property, and executes the required INSERT, UPDATE, or DELETE statements iteratively for each row, based on the order of the indexes configured in the Data Set.
I'm sure there is an extremely simple reason that this one line isn't working, but it has evaded for the past week, so I'm hoping someone else will notice my fault.
NET Framework data provider to connect to a data source and Command objects to retrieve data from and resolve changes to the data source.
The Sql Data Adapter uses the Connection object of the .
So if you would try to omit that line the changes doesn't reflect in your datasource as what you have noticed..
This is the reason why I am asking whether it is mandatory to update the Data Table first before updating the data source? As what i have observed in your code you are just Updating the values from your Database and not in the Data Table so thats why its mandatory to have that line you have commented out..
If your application never sends those changes back to the data source, then you are finished with the update.If you do send the changes back to the database, then a second step is required.If you aren't using data-bound controls, then you have to manually call the Update method of the same Table Adapter (or data adapter) that you used to populate the dataset.It has been working fine, until I switched computers. Now the Dataset is being updated, but the Database is not. Command Text from the two and they are exactly the same as are the Item Array data elements. In order to update the data on the database your Sql Data Adapter need to have its Insert Command, Update Command, Delete Command properties set.