Why not just store the information in the database, and relate it to the user's ID?
On 3/30/06, Jeremy Bunton <[EMAIL PROTECTED]> wrote: > I have an application that has many forms that are saved in sessions as the > user jumps from page to page, allowing them to see what they had entered on > any page at any given time. Now the users want to be able to hit a button, > save the entry and come back weeks later and see what they had entered. Now > I need a way to save all sessions to a file, perhaps text or something. So > that the user can login say 3 weeks later select the saved criteria (which > there may be 50 different ones of by now) and then have all the forms > repopulated with the same data as before. Any ideas how I might get that > done. -- ======================================================================= Raymond Camden, Director of Development for Mindseye, Inc (www.mindseye.com) Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia) Email : [EMAIL PROTECTED] Blog : ray.camdenfamily.com Yahoo IM : cfjedimaster "My ally is the Force, and a powerful ally it is." - Yoda ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:236564 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
