Hi!

I do not know wwIPStuff so well, but when you use DLL, the DLL might allocate some resources or wait for certaing event inside of the DLL. When you try to deallocate DLL from memory, it hang up just because that. Try to explore more documentation on the working with HTTPS using wwIPStuff, maybe you require to call some function of that DLL before you clear it from memory, something like HTTPCancel()...

HTH.

>I have an application written in VFP6 that uses wwipstuff to fetch files via HTTPS from a web server over the internet. The file transfer functionality is working fine, however at the client site on the NT Server box where I'm running the app, it hangs on the way out on a CLEAR ALL command. Thinking that it might be one of the DLLs that wwipstuff declares, I inserted a CLEAR DLLS in front of the CLEAR ALL and it hung on that statement instead. If I remove these CLEAR statements, it hangs as well. The app doesn't hang on the way out if I don't execute the code that creates the wwipstuff object and does the file fetch, so it seems like it is tied to the wwipstuff class. Does anyone have any idea what might be causing this?
>
>I have tried the application on some other machines in our office and don't encounter this problem - it exits normally.
>
>One other piece of information - I am running the app over a PCAnywhere connection into the client's machine, so there is a PCAnywhere host running on the box. Since this app will be eventually be scheduled to fetch files periodically in a "batch" mode, I tried scheduling it, exiting the PCAnywhere connection and letting it run unattended, but when I reconnected to see how it made out, the job was hung and not responding just like in the interative mode. Could the PCAnywhere host program have any connection to this problem?
>
>Thanks in advance for any ideas.
>
>Scott