This means that when the user does an update, the data from that update is lost.
You should create your data source once (on the user's first visit) and store it into Session for later use, and only bind the Grid View to the data source when it is necessary to do so.
I'm having a very hard time understand what would prevent your event from being fired.
Do you have some sort of Java Script functionality that may be stopping it? A common problem people have with Grid Views is understanding when to data bind the data source to the Grid View.
As far as I can tell, all of the properties are identical between the Grid View that is working properly and the one that isn't.
Since I don't know enough about the underlying code responsible for calling the Row Updating event, I'm not sure how to debug this or what things to try.
You have to make sure that you aren't setting your Grid View's data when it is not postback.
If you do this, your Grid View's source will be refreshed before you're able to grab the new values out of it.I would recommend trying this out and starting a new thread in the .NET Forum so that other people can learn from the experience too. -Frinny You may need to turn off validation even if you are not validating anything.Right now, I have not written code for the Update event. Right now, I have not written code for the Update event. Then the page posts back, the text boxes go back to being labels and the new values are lost, and the Row Updating code never fires. Yes, I did put the breakpoint at the Row Updating line (and not in the function).For some reason when you click "Edit" to edit the contents of a row, then "Update" the Row Updating event is never called (i.e.