You can work with the Keys, Old Values, and New Values collections before the values are passed to the data source.A typical way to use these collections is to HTML-encode the values supplied by the user before they are stored in the data source. For more information about how to handle events, see NIB: Consuming Events.
To cancel the update operation, set the Cancel property of the List View Update Event Args object to .I have some code that is identical in Item Updating and Item Inserting The only differnce is one use Values(). There's really no built in way to grab the previous values in updated. String() the other Item Updating used New Values(). What you can do is, in updating: Session["old Values"] = e. Developing a Sharepoint application would have all the fun of a video game, if only you had infinite lives.
Dangers lurk hidden out there which, if you run into them, can be a blow to your project and waste a great deal of time.This is to summarize the inconsistent behaviors I encountered when working with "After Properties" in "Item Updating" event handler on a custom Share Point list in SP 2010.