Timeout when loading gridview (viewstate suspected culprit)

[fig000]

Hi,

I have a simply app which loads a gridview with perhaps 25 fields
per row. Each row can be edited, updated and deleted in the classic
gridview way (no forms for individual records). I set it up this way
because the point of this app is to maintain some fields and generate
a spreadsheet so having the grid look like the spreadsheet, without
pagination, is best. I did try pagination and it didn't solve the
viewstate timeout problem..

What I've found as I've been testing and the data has grown is that
the page is timing out. From past experience I suspect the viewstate
being big (25 columns times perhaps 400 records). It really is the
most practical way to keep the app from a visual point of view though
in addition to the loading time out, the loading of edits and updates
has a similar behavior; it times out. I looked at the trace on the
error page and it seems to go past the sql stuff to the page rendering
code, strengthining my feeling that this is a bloated viewstate
problem.

I has playeed with http exection time out in the web.config and
looked into some other possbilities. I figure turning off viewstate
would kill the grid. Is there some way I can late bind this and speed
up loading the grid and the update capabilities. I could even live
with it as it is as long as it wouldn' time out.

Any advice would be appreciated.

Thanks,
Fig

 

[Peter Duniho]

[...]
What I've found as I've been testing and the data has grown is that
the page is timing out. [...]

Any advice would be appreciated.

Sure, happy to help: post your question in the ASP.NET newsgroup, where
you'll find people who actually have run into this issue and understand
how to deal with it.

Pete