You may need to rebuild the datasource once you modify the table to get it work correctly.First of all, the Data Source that is being used to populate the Drop Down List is a bit different.
Here is an example of one of these that uses the Select and Update commands.
" Select Command="SELECT * FROM exg_Forums WHERE forum [email protected] ID" Update Command="UPDATE exg_Forums SET [email protected],[email protected],member Create [email protected] Create Thread, sort [email protected] Order,[email protected] WHERE (forum ID = @forum ID)" Delete Method="Delete Pipeline User" Insert Method="Save Pipeline User" Select Method="Get Pipeline User" Type Name="PTCPipeline.
However, of you set up your Table Adpater to automatically generate Update statements, it will send it as @original_Employee ID, which is why original__ is the default value for Old Values Parameter Format String.
The Grid View will automatically pass the Employee ID to the Delete Method, there is no need to put it in the Command Argument property.
The Textbox values come back as empty, which is even stranger.
Below is the code for both the Grid View HTML and the C# code behind.
Using the wizard will affect your other (SELECT, INSERT, DELETE ) calls if you are not careful.
If you have the option, I would recommend using the SQLData Source objects.
Scenario: I am using the Row Updating Event of the Gridview to do updates because I need more flexibility than the SQLDatasource Update provides.
You will have the flexibility of working with your SQL directly in your file and you don't have the contrains that the Object Data Source has.