Yes, you can use the Session object for this. Just use:

Set Session("oYourRSNameHere") = Server.CreateObject("ADODB.Recordset")

This doesn't put any overload on the Session object itself but if the recordset is large and you have lots of users, it could overload the server by using up available RAM. If you do this just be sure you create and load the object as late as possible and destroy the object as soon as you're done with it.

Another possibility is to use cookies to store the data elements on the user's machine as you go from page to page and then create your insert on the last page loading in the data from the cookies. This avoids the server overhead of storing the data in the Session object.

HTH

>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