Use an ObjectDataSource and bind a repeater/grid to it then enable the in built caching :
http://www.asp.net/Learn/D
Main Topics
Browse All TopicsHello,
I have a page with a table in UpdatePanel that is dynamically populated with a large amount of data, takes some time to retrieve. The table has LinkButtons in it to drill-down on that data, which is then displayed in a hide/show div. Problem is, since it's a postback, the original data has to be retrieved again - I'm trying to avoid this since it takes time but it's the same data that was retrieved before postback - I just want to retrieve the drilled-down data and show it. If I put the retrieval of initial data in (!IsPostBack), then it, of course is not retrieved on postback and is not showed. Is there some kind of a workaround?
Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Use an ObjectDataSource and bind a repeater/grid to it then enable the in built caching :
http://www.asp.net/Learn/D
Our report table does not have a regular row-by-row structure (I would've used GridView otherwise) and then the data retrieved uses several ad-hoc queries... Haven't thought about session, though - I am fine with the users having to wait once in a while (when it expires). Still interested if there is a way to do without resorting to session, but session works in this case!
Business Accounts
Answer for Membership
by: brawneyPosted on 2009-01-08 at 15:26:45ID: 23331341
Sounds like you might want to use a Repeater (http://weblogs.asp.net/an asghanem/a rchive/200 8/09/06/ co mparing-li stview-wit h-gridview -datalist- and-repeat er.aspx) and (http://msdn.microsoft.com /en-us/lib rary/ syste m.web.ui.w ebcontrols .repeater. aspx). It will keep the data in the view state and you won't have to refresh it. But the view state can get a bit large so be careful of that.
la.com/art icles/1009 02-1.aspx /Article/2 7327 en-us/maga zine/cc301 579.aspx
Another option is to put the data into the Session once you've retrieved it for the first time. You'll still need to populate your table (or Repeater) with the data on every post back, but you'll get it out of the Session instead of having to go back to the database.
You may want to look at using the Application Cache in the same way, but be aware that the Application Cache is Application wide, so the data pulled for user #1 would be the same data given to user #2 when that user hits the page and it goes to get the data out of the App Cache.
http://aspnet.4guysfromrol
http://www.devx.com/dotnet
http://msdn.microsoft.com/