i want to say one more thing i call the display method at the end of every event which i handled ....

gridview rowupdating commandfield-43

In your Grid Views On Row Updating event you will call your data access layer's methods to do the updating.... -Frinny @Frinavale You said that we have to bind object with grid view at page.prerender . What happens is that the View State for the Grid View is loaded just before the Page Load event.

I think if we do the same thing on page load event it work because value is set when row updating event is fired. This means that all of the data that the user provided for the row that they are updating is loaded into the ASP.

Wouldn't it be easier if you just had to call it once?

That is why I recommended that you do this in your Page Pre Render event.

I want to use this method so I can do an update in grid view directly. Grid Views can bind to Data Tables, Data Views, Arrays of Objects ..more.

I've never actually used the Sql Data Source before. So, you need to populate the object that you are going to use as your data source at some point in your page life cycle.

When this event fired it saves the values at their view state & this view state is sent to the client. NET controls used to access the data in your C#/VB. If you do a Data Bind in the Page Load event then all of this data is lost!

Edit: if you do a Data Bind in the Page Load event every page request all of your data will be lost It's the most common problem that people have with Grid Views that I've noticed.

I like to be in more control of my database connections. You could do this in your Page Load event if you want to.

You could cache the object that you are going to use as a data source too.

:) -Frinny @Frinavale Frinny I send You a code , By the way You are so senior & i respect each & every word which you are writing for me....