Users can change data like the number of moons or the distance to the earth, but they are not able to change the name of the planet.
To prevent users from changing the name of the planet, you can develop a Item Updating event receiver.
I have to click Edit and Cancel twice for them to do their action.
The legacy code in the SQL data source used a update statement with parameters.
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.
So the question is: What is a good technique that can be implemented such that I can check whether a specific column in a list changed in the The blog post James's colleague wrote is wrong.
If you follow the link he uses you'll see the table for lists he uses is different from the one he references.