Event itemupdating which wasn

Do you absolutely need to do something Asynchronous?

Event itemupdating which wasn

I just noticed after the first time it only takes 1 click to get into edit but still 2 clicks to get out of edit mode.

I just relised this is because the detailsview is not rebound when you go to edit.

I seem to have a problem with mode changing when using my detailsview control. protected void Detail View_Mode Changing(object sender, Details View Mode Event Args e) Now, when I click on edit or insert and trace, the program hits the right event, but I have to hit the button twice for the control to change mode.

Even when it does change mode, regardless of which control I hit, the program will randomly decide if it is going to go into edit mode or update mode.

I have to click Edit and Cancel twice for them to do their action.

The first and second click are calling the Mode Changing method so I assume there is something wrong with my code and the same with just B's code.

I use these rules of thumb not to have to look at that post all the time: So if you want to test if a specific column was changed you have to use the Item Updating instead of the Item Updated eventreceiver.

Is there a reason why do you want to use the Item Updated receiver specifically?

This demo is basically how my web app works with objects instead of SQL. protected void Details View1_Mode Changing(object sender, System. Thanks heaps for your help I was about to split up the page into three seperate pages for view, edit and add because I couldn't work it out; but I didn't want to because Edit and Insert are basically the same.

Tags: , ,