Everyone, So no one trys to wrap his or her head around this I will tell you I found the answer. Despite the fact that the trace on on the error page "seemed" to make it through the sql and was rendering, that wasn't the case nor was it the problem. I found that if I put the sqldatasource command command timeout to a large number (I put 6000 which I stole from another posting), the app works. Hopefully someone will learn from my mistakes. I guess learning the true event heirachy for a page would be a good idea. I think one of the downsides of our RAD data presentation controls is that you tend to ignore other issues because they work so well most of the time.
It's still slow. I had considered using some ugly dynamic html table to render this instead of a gridview so it would be fast but then creating the spreadsheet easily from the gridview wouldn't be an option and I'd have to find out how to build a spreadsheet using excel objects or something equally time consuming. Sorry for whatever brain bandwidth was used to think about this. Live and learn :-(, Thanks, Neil On Jul 29, 12:59 pm, fig000 <[email protected]> wrote: > 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
