Recently, there has been several threads on maintaining the state of a Web Service. I would like to mention that I wrote a 2nd article on that topic in our July issue of the magazine. SOAP 3 provides a greater flexibility in achieving that task. The article mentions one approach which is by the use of the ASP intrinsic objects, from within VFP, combined with the management of a cookie. This works great and no longer requires the client to do extra manipulation to forward back a header, a cookie, etc. as this is done transparently such as when you access the Universal Thread. The same is true from the server side, as you no longer have a establish another DLL for the SOAP header or to manipulate extra data. Basically, it's the same approach as a Web application, such as we do here, to recognize the user.