Thanks Paul,

I will give this technique a try this morning after polishing my new "chrome dome".

Glenn

>>
>>Since converting to VFP8.0 this process no longer works. The upload occurs and then we get a 12002 error and there is no download. Our customers are VERY upset with us and we need to fix this NOW!
>>
>>We have set the oHttp.nConnectTimeout to 360 to allow up to 6 minutes and it does not wait any more than 3 seconds. We are using wwHttp version 4.40. We have erased all the FXP's , used wconnect.h ver 4.40, made sure the wwipstuff.dll is compatable and finally ripped out ALL of our hair!
>
>I had a problem just recently with wwIPStuff and it turned out that I needed to set the timeout immediately after creating the first instance of the object, and before it was used at all. What I mean was, I had code that created an instance, connected, downloaded some things, disconnected and went out of scope. It didn't need to have the timeout changed. Then I had some other code that created another instance, set the timeout, connected and downloaded stuff but STILL timed out way before my timeout setting. As soon as I set the timeout in the first bit of code, everything started working.
>
>This is under VFP 8, with wwHTTP 4.40. I've also gotten in the habit of making absolutely, positively sure that there aren't any other versions of wwIPStuff.DLL anywhere along my search path , and I pass the path to the directory where wwIPStuff is located when I create wwHTTP:
>
>

>loHTTP = CREATEOBJECT("wwHttp", FULLPATH(CURDIR()))
>loHTTP.nConnectTimeout = 360
>