>>Has anyone figured out how to maintain the session state when using SOAP? The same code when accessed from an ASP page by just invoking a COM which deals with the session object to return the same SessionID works well for each transaction. But, when that is under SOAP, the same code returns a different SessionID for each transaction when the COM is under a Web Service.
>
>Check this article called Managing State in XML Web Services Created Using ASP.NET:
>
>http://msdn.microsoft.com/library/en-us/cpguide/html/cpconstatemanagementinaspnetwebservices.asp?frame=true

Yes, from what I've seen in the recent days, it seems to be a piece of cake to achieve that with a .Net Web Service. However, we don't have that ability in a Visual FoxPro Web Service and this is where I am trying to make that work. I've converted the approach to use ASP listener with the low level approach. Only whatever I initiate as per the cookie or the session, does not come back on the next transaction.