Yeah, I would totally do that.. EXCEPT that the page building the recordset based on the original POST value is being referred to from a previous page with a dynamically built list of records. I can assign the uniqueID of each of those records to a POST value so regardless of how many records there are, each will POST with their own uniqueID to the secondary page for editing. Because that list is dynamic, I can't hard-assign a Session variable to each record. Make sense? Or can I???
Better description of flow:
Page A has a database delivered dynamic list of Customers, each with it's own uniqueID.
A form exists for each record in this list, allowing us to POST that uniqueID to Page B without showing the ID in the URL.
Page B retrieves the record based on the uniqueID in the POST value, and populates the Update form values.
Page B also has a dynamic list of Users for each Customer, with it's own form to POST a UserID to an Update page to change user record on Page C.
User Submits the UPDATE on Page C to update the User record, and is redirected back to Page B.
Page B fails to load the dynamic list, because it's missing the POST value from Page A.
...clear as mud??
