>I would not answer your questions, just will propose you some workarounds.
>1. Instead of using Session and Response.Redirect, why not use the Viewstate and Server.Transfer? Yes I know that viewstate is not encoded hardly and travels back and forth to the >client browser, but you can encode the userid, before adding it to the viewstate. Note that when you use Server.Transfer you may have access to properties of previous webform from >the current one, this way preserving the USERID. (You should add a property that will get and set the USERID from/to the viewstate for each of your webforms.)

I thought ViewState was tied to the web page and would not cross pages? Is this not the case?

>2. What about (re)adding USERID to session object, just after the assign of VFPCOM_RCW instance to null e.g.

Do you mean save it prior to hitting the VFP dll and then resetting it after I have closed it? If I do that then the Session isn't really doing anything for me? What about all of the other session variables?

This has been a bit frustrating - thanks for everyone's help.

Doug