[eluser]adamp1[/eluser]
How many people use pagination and say have a filter to reduce the results down? I know I use this a lot but am having huge problems when it comes to passing all this data around in the uri so I can return the user to the correct page after say they modify a record.
Its just not possible to keep passing all this data around through the uri like I would have done if I had GET variables (I know I could turn them on, but then it means the use of urls through the application isn't consist, which I don't want). So does anyone have any clever idea's of how to pass all this data around?
The data that would need to be passed would be, what offset you are on and any current filter options.
I was thinking if it was stored in flash sessions that may work, but what happens say if you are on the last link of a pagination trail and there is only 1 row. If you delete that row how will it know where to return to, since if it goes to the page it
was on then it would be invalid, due to no rows for that page.
This was getting discussed slightly on another post but I didn't want to hi-jack it any more than I had done already.