I'm still having issues with this and would love to hear from more people \nabout how they are approaching this issue.\n\nAfter thinking about all the ways to pass arguments to a Web form (query \nstrings, context items, application objects, view state), I started favoring \nusing the Session object. I created a generic method that retrieved a \nvariable from the Session object and then deleted it so that I didn't end up \nwith a ton of unused variables for each user.\n\nThe problem with this approach is that, if the user hits refresh, all is \nlost. My view state is gone and, since I deleted the session object \nvariables, they are gone also.\n\nI looked into PreviousPage.ViewState but this does not seem to be available. \nAlso, I suspect a refresh would trash that as well.\n\nEverything seems to be pointing to query strings. But I hate the fact that \neven the most casual of users could modify the query arguments (or just type \nthem wrong) and end up changing someone else's data. I know I could perform \nverification of the user, but for some tasks, this require additional trips \nto the database, which I would like to minimize.\n\nHow is everyone else doing this on sites that require the user to be logged \nin?\n\nThanks.