Following fixes this.

InitializeComponent()

{

(g1_PageIndexChanged);

 Hello,

It is really hard to figure out what is going on without seeing the code, I do have some suggestions though that may resolve/alleviate the issue

1) Use the built-in asp:UpdatePanel instead of WebAsyncRefreshPanel. WARP was originally designed before UpdatePanel was released and is intended primarily for ASP.NET 1.x backwards comatibility (where UpdatePanel is not available).

2) If you have anything related to the grid that is programmatic (e.g. with code), try moving it in different stages of the page lifecycle. For example if you are creating the grid dynamically, move it to the OnInit event of the page, etc

3) Try databinding the grid either declaratively (using declarative datasources) or using the InitializeDataSource event - this event gets fired whenever the grid needs datasource - for example for paging - and could be the better place to databind the grid.

HTH,

The warp should be able to access datavalues for any input controls on the form (not just the ones inside of the WARP panel).  However, you can not set or update controls which are outside of the warp panel.  I usually place my buttons inside the WARP or UpdatePanel just because it doesn't add a whole lot to the weight of the request/response, and it automatically gets hooked up (no need to add triggers).

To really understand what's going on, you'll probably need to step through your code and see what code path is being taken during an async call.

-Tony

I think my issue may be related to this:

 I have several controls (dropdownlist, buttons) outside of webgrid. I would like these controls trigger the grid to do thinks like go to different page, reload data. I also like this is an AJAX-like call: the button event handler can load the data and bind the data with the webgrid without refreshing the whole page.

Should I put the webgrid in a warp or put all these controls inside a warp?

Any examples?

 Thanks,

Guangming