Itemupdating which wasn t 100 free one to one sex chat


That happened to me as well whenever I changed the Data Source or Data Source ID in Page Load.

If I needed to switch the Data Source for the same control I had to do it elsewhere or come up with a scheme as the one mentioned earlier. Whenever an event fired that I wanted to change the viewmode for my form, I just store the right Form View Mode type in that object.

itemupdating which wasn t-78itemupdating which wasn t-27

Jono Hello everyone, I'm back with an example that anyone should be able to try which shows the problem.

If you do the example without the Mode Changing event you get this error when you click the Edit button: "The Details View 'Details View1' fired event Mode Changing which wasn't handled." You don't need much ASP.

So i changed the Is Post Back if statement, I'm not sure why the databinding makes you click edit twice. Details View Mode Event Args e) Cancelling would go from Edit mode to Read Only mode, which not rebinding may be the problem you are having, emphasize "may be".

If you have any problems getting the demo to work let me know. I fixed this by doing the same thing as you suggested for Mode Changing by databinding but I also had to set the currentmode to Read Only.

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.