When in edit mode, I want to display save/cancel icons to commit or cancel the update.I can see the control switch to edit mode properly, but after clicking the save icon, the overriden Item Updating event that I wrote does not fire. The Mode Changing and Init events fire because they specify a Handles clause.

asp net detailsview itemupdating-72

These features are fairly amazing, because you can achieve this “edit mode” without writing any HTML at all: the columns know how to render their editable modes by themselves.

If you don’t like their default edit mode appearances, you can customize them using templates.

This property is provided to make the control more accessible to users of assistive technology devices.

controls effectively, we need to know how to handle their events.

I was then able to go back to my test page and drop an ODS connector on there and attach to the custom select and update routines. I created the Details View Data Binging sub which populates the field using a datatable 4. Everything works with any issues, just no data is ever returned. Mode Changing '# When the form mode changes we handle how the form loads and what it looks like here Select Case e. Edit) 'Bind Details View() 'Put into insert mode Case Details View Mode. Read Only) Bind Details View() End Select End Sub Protected Sub Details View1_Item Updating(By Val sender As Object, By Val e As System.

I bound that to the Details View and low and behold it works! Why is it when I use my own Data Binding routines (which bind to the data just fine) in a code behind page that I have issues when it comes to the Item Delting or Item Updating routines? I created a Mode Changing Event handler to allow me to change the mode into EDIT mode 5. I hope these shed some light: DETAILSVIEW1 ################################################## ############### Protected Sub Details View1_Mode Changing(By Val sender As Object, By Val e As System. New Mode 'Put into edit mode and databind Case Details View Mode. Insert 'put into read only mode and databind Case Details View Mode.

Is Post Back is always true when the Init for the Details View is called.

How can I distinguish the initial load from subsequent ones? If the data binding does not happen again, does the server just keep loading the data for subsequent postbacks from View State? The Mode Changing and Init events fire because they specify a Handles clause.

The Item Updating event also specifies a similar Handles clause, but it still does not fire.