I am designing a web-application where I need to save a parent record together with its children, where the children may be selected from existing entities, with the option of creating new child-entities in another ASP-page, then returning to the child-selecting page.
To accomplish this, I was thinking of either using a VFP-dcom object or (possibly and) a hierarchical recordset, saving only when the entire parent-children structure was complete.
To do this, I would need to access this object (recordset or VFP-object) in several ASP-pages. So, the question is:
Can I use the Session object to keep this object, or is this a Bad Thing, putting to much overload on the Session object?
Secondly, is this at all a reasonable way to do this kind of thing, or am I looking in the wrong places?

Thanks in advance for any advice...
Arne