>You've got a few options - GET parameters (eg. pass them in the URL), POST parameters (hidden form variables), session variables, or if you've got a large data entry screen, what I tend to do is create a table w/enough rows for all of the data (denormalized, obviously). As the user fills in each field/set of fields, I store this info into the table. One of the fields in the table is some sort of identifier I can use to tie the session to the user ( usually the session ID: Session.SessionID). This makes it really easy to handle a lot of common information between pages.

Ok, I'm confused why would you simple put the objects into Session? Isn't that what the session is for? I mean, if you are going to be using data across multiple pages, I think that place for it would be the session. Why create the table and store the information there, and then have to connect to the database on every page request to get the information from there?

Morgan