Fired event rowupdating which 100 dating in international new site zealand
Most Web Developers have come across this problem at one time or another, how do I stop someone navigating away from a page if they have not saved any changes they have made?
The answer is that you need to employ ‘Dirty Checking’, basically set a flag when the page data is changed and check it if the user tries to navigate away.
Note that the Save button is configured to clear the Dirty Status (i.e. However, as the Grid View only held part of the information on the page we wanted it all to be committed at the same time, i.e.
This could easily be caught in the Row Updated event and seemed a logical choice and initially seemed to work as expected – until one of those damn tester people got hold of it.
So now we could flag a page as being in Edit Mode and bail out of check Exit if it was (even if the apge was flagged as being dirty).
But we were not out of the wood quite yet – we still needed to wire the new functions into the rest of the code.
If they make changes to the data fields and click OK then the flags are reset accordingly.
Now we just need to handle the situation where the user clicks on the Cancel button of a row in Edit mode. It may not be the only, or the best way but it solved the problem that we encountered.