If we use proper command names for the buttons like “EDIT”, “DELETE”, “UPDATE”, “CANCEL” these will also trigger the appropriate Grid View Events.Ok let’s move on to Code behind what we have to do when user clicks Edit, Delete, Update and Cancel When we click on Edit the On Row Editing event will be fired.Here logic is to check which button is clicked by user is it insert button or update button.If its insert it will perform insert action which is “if” block and if its update then “else” block will be executed.You can see the C# code below will give the row number whatever you are editing by New Edit Index property.
Now these listed features are very much required, as we list data user may want to sort it or edit it and of course paging is also necessary to show large amount of data divided into pages.It is the exact, perfect and great solution to your problem!Today was spent mostly tackling the Grid View’s Update/Edit functionality, and I got incredibly frustrated, at first. So be sure to rebind your Grid View at the end of your event handler. I’ve got a pretty good handle on it as I’ve been doing it for several years, and can help with a lot, but I definitely don’t claim to know everything.I suppose my eyes got big when I saw all the new properties and methods, and wanted to try them all out. Most articles I found were for hardcoded datasources (especially on MSDN, ugh) and didn’t really help me much, so this post will be referring to Grid Views with dynamically bound datasources. First, create a Grid View with three bound columns and an Update/Edit/Cancel (Command Field) column: Nothing in there should be shocking to anyone: all your events are handled, you have a Hyper Link Field that uses the Data Navigate URLFields property to insert a Product ID, and you have set your Data Key Names property to your hidden field which holds your Product ID. aspdotnet-suresh offers C#articles and tutorials,csharp dot net,articles and tutorials, VB.