>Well, for sure, you will not have an access to the response object as this is a server object. What I have done close to that, was to enable a cookie container, for a Web Service client, built in such interface, so once I send another request, the cookie would then be sent as well. If the cookie container is not set, whatever will be sent will not include the cookie that the server sent in the first place. But, in your case, you want to build the entire cookie container on your side. There is probably a way to do it.

I've had a hunch that the Response object was a server object. The question becomes where would I put the cookie container? The app is an MDI app, and I'm using the Parent Form to hold a few properties that need to stay available throughout the course of the execution - could I stash the cookie container there, as a property? For that matter, after I've created the cookie container (and the cookie), could I force another request to get the server to recognize the new cookie?

Perhaps dumb questions, but these are new waters for me. TIA...

David