Recently I was tasked with encrypting/decrypting some data that could be edited using ASP. Along with the details view control, the legacy code used a SQL Data Source to select and update everything.

This means the data access layer was bypassed completely, so any business logic that dealt with encryption on this page had to use a different execution path. The problem could be divided into two tasks: The first task was the easier of the two, as it just involved referencing the encryption library from the code behind page and calling the function inline in the aspx page.

After setting the Details View’s Item Updating method, you will need to modify the SQL Data Source’s Update Command, Update Command Type, and Update Parameters.

The legacy code in the SQL data source used a update statement with parameters.

NET 4.0 (Web Forms) A snippet of code that I believe to be relevant below: The problem is that if I want to handle the old values, I can´t: this, evaluates to 0: int old Values Count = e. Count; and this, evaluates to null, even if I alter the value to a new one: string company Name Old = e.

If it's bound via Linq Data Source, Sql Data Source or Object Data Source I suggest you have a look at the Updating Event.

However it seems that if the value coming from the Details View is null for Field1 then e. Is there an easy way round this, i am putting the values of about 10 fields into one string variable, i want to avoid 10 if (e. = null) If you just want to avoid duplicated code, why not move it into another method?

It's not so much code duplication i am tring to avoid as having to do a load of comparisons to see if a particular value is set or not. New Values("Some Field") to a function/method is that if Some Field is set to null in the Details Views control then rather than there being e.

I have used the Item Updating event handler for the Details View and i am populating the Mail Message. New Values("Some Field") with a value of null, it simply does not exist. "Flinky Wisty Pomm" wrote: If you just want to avoid duplicated code, why not move it into another method? For more information, see Validation Server Controls. The Details View control can automatically add a Command Field row field with an Edit, Delete, or New button by setting the Details View. Unlike the Delete button (which deletes the selected record immediately), when the Edit or New button is clicked, the Details View control goes into edit or insert mode, respectively. Validation server controls are also provided to assess user input. Auto Generate Insert Button properties to true, respectively.The product table is not updating with the new values.I think the problem is to do with the new values from the textbox not being retrieved. To declare the row fields, first set the Details View. When both are used, explicitly declared row fields are rendered first, followed by the automatically generated row fields. However, to make use of the Details View control's advanced capabilities you must explicitly declare the row fields to include in the Details View control. The row fields specified are added to the Details View. Note: Explicitly declared row fields can be displayed in combination with automatically generated row fields.