put the 1 table in a Dataset. Do a .getxml on the dataset and put that string in cache rather than viewstate but hash its name for the user uniquely.
2.0 Datasets rock btw 2.0 is generally pretty mediocre (Anders the real brains left and Nikhil and Guthrie are porr substitutes) but Omri Gazit's ADO.net team did a good thing in 2.0 http://tinyurl.com/65adh is an awesome article dealing with the dozen things in ASP.net 2.0 I am looking forward to. I wish there were more than a dozen things but MS really is getting complacent and yacking/bragging more than shipping. On Mar 30, 2005 4:00 PM, paputus <[EMAIL PROTECTED]> wrote: > > > Hey Guy's > > I am looking for a good and efficent way to handle a datatable that > can potentially be very large in a user control that uses the same > datatable in a few different ways. > > Currenlty I am placing the datatable in viewstate, and having the four > other countries not use viewstate, and jsut keep goign to that datatable. > > My question is... this viewstate can get to be tremendous..if i have > say 200 or more rows of data. ( I must have all rows available > becuase one or two of the controls on the page can be using the entire > set for a list. ) > > Any ideas? > > Thanks, > Jonathan Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
