Dear Friends

I have developed a module "Biodata" and it contains two user controls

1.ViewBioData.ascx

I have a dropdown with "Classes"  loaded in viewbiodata.ascx. Depending upon the class selected, the list of students in the class will get displayed in a datalist.DataList contains the list of student name in the datalist with paging and sorting. On Clicking a student name, it would redirect to "ShowbioData.ascx", which would show the bio data of the clicked student. I have a back button in the showbiodata.ascx clicking which it must get to the viewbiodata.ascx page with the datalist being maintained and also the page from which i clicked initially.

My Problem is  I have implemented the other things, but on clicking the back button, i could not maintain the initial datalist and the paging in viewbiodata.ascx

kindly guide me in resolving this issue.

All replies are appreciated.

regards

deepak

As was mentioned above, Option #2 is the "DNN" way of doing this and is probably the best in that emitting the current filter, page, StudentID parameters on the querystring allows the user to easily bookmark the details view.

A fourth option is to use only one control with the appropriate mechanism (Panels, MultiView, ListView/DetailsView control, etc.) to hide the list/reveal the detail, etc. without having to redirect from control to control. With this approach, v13wstat3 will be available for maintaining page state. A variation on this option would be to have one module control containing the list and have that dynamically load the detail control as a child control. I often prefer the latter approach when giving the user a choice of several different detail views. 

Both very good points by Will and Mamlin.  I tend to forget the fourth option (as evidenced by my post) because I tend to steer clear of it wherever possible.  I am one of those purists (whether a good thing or not) and hate to bloat my pages with extra stuff that may or may not need to be on there depending on what the user ends up doing.  I really like MSAJAX because it is "easy", but oh how I hate it because it still posts back everything on its Callbacks. 

Completely off topic for managing state but related to the AJAX thing brought up -- I just completed a project that has a single .aspx page (yeah, not a DNN module though I *could* have done it as one).  All the content is stored as HTML snippets in several HTML files, then I use AJAX and jQuery to dynamically populate each section as it is accessed and completely replace the content from the previous section.  In other words I have a single placeholder DIV that I load the new "sections" into as they are requested and use jQuery to make the transition beautiful and smooth.  Then all the data is accessed via webservices using the MSAJAX framework (though I suppose I could just as easily do it with jQuery and reduce on javascript bloat... on the other hand, I'm using the scriptmanager to combine the scripts into a single request anyway so after initial request it is all cached anyway).  Long story short though, it is BEAUTIFUL and works GREAT.  Nothing like little 200 byte to a max of 2kb requests to handle everything.  Booyah!