session("datepicked") = Rs("Start_Date")
Then,
strDATE = session("datepicked")
response.write strDATE 'on other pages.
This goes with what mattfairw stated about session data. It is something I would use in this case. Set your session timeout to a length based on how long you think your users will be on that particular site.
Main Topics
Browse All Topics





by: mattfairwPosted on 2005-05-16 at 18:21:53ID: 14015463
if i'm understanding your question...that may be a bit difficult. you could pass queary strings to all your pages which would be cumbersome...or could have hidden form fields which could be cumbersome...or you could use session variables, but that wouldn't work if the user had cookies disabled on their machine. If your user needs to log in first, you could add a column to your database containing their last date chosen and a second column containing their current session id(which you grab using ASP but i forget the command right now). then when the user goes to the calendar page, check and see if a session exists for their account...if so, see if it matches their current session id...if those both are valid, then you can read in the previously chosen date value and use that. the session id is used to make sure you're only loading the previously chosen date if the user is still on their original session. if they close of of the browser, and go back to the page, then it wouldn't load the date and they could choose a new one again, this could be omitted if that's not the case. Also, when the user does select a date...amke sure to update their DB values
This seems like a bit much, and i may be missing something obvious...its been a long day ;). Cheers