As in from a Web Service to an ASP page?<BR><BR>Or as in retaining the dataset in memory for 20 minutes while you wait for the user to push a button on one page that will take him/her to the next page?<BR><BR>Or what?<BR><BR>
Like, information in the web form is kept in the asp.net page, and finally, in the summary.aspx, the dataset's information will be retrieved to store into a database's table. The page where the dataset is created is not the same as the summary page, which is also a aspx.
...but you have to decide whether it's a good idea to do so. A dataset could eat a bunch of memory, and if you tie up that memory in the cache for 5 or 10 or more minutes...well...is that *really* a good idea?<BR><BR>Only you can tell.<BR><BR>Anyway, caching in ASP.NET is easy. Here's one article on it that keeps it pretty simple to understand:<BR>http://www.codeproject.com/aspnet/caching.asp