The most common set of receivers used, however, are part of SPItem Event Receiver which let you wire your code up to a number of events that can occur to items on a list or library.
When working with events, you’ll quickly find that before (synchronous) and after (asynchronous) events exist, and the method suffix such as “ing” (e.g. Item Added) will tell you whether it gets invoked before or after the actual change is made. And, as you get deeper, you’ll even find that you can extract the before and after state of the change.
I am using a Details View to update an existing SQL Server record.
The columns from the sqldatasource display fine in the Details View and I can edit them.
For example, you can hook into the Item Updating event for a document library and prevent a user from changing a certain column.
The code might look like this: When they say “not available for post events on list items”, do they mean after events (like Item Updated, Item Deleted, etc)?
Like it expose you the property Keep In Edit Mode setting it to true, doesn't change the Display Mode of the List View.
Here's the button click event that was having an issue: I still don't know why your data is not being updated, but as far as the design is concerned, why not go with Grid View/Details View combination with two Sql Data Sources?
The wording is curious here, so I thought I’d take some time to test each combination of common events such as Add, Update and Delete.
These were done across a custom list and then a document library.
In this scenario handling the Updating event of Linq Data Source would save you from handling same events for each Presentation control.
On the other hand using the event handler of the List View allows you control on the underlying presentation control.
Each test involved adding a new item, editing the item and then deleting the item.