>Yeah, I wasted a ton of time trying to track that down. I'm sure there is some caching going on with this, and it actually does have some useful side effects. For example, you can write a method that hits a website to establish a session. In another method, you do some other operation w/o having to reinitialize the session. You don't need to share an instance of the object between the methods for this to work. I wonder if there is a way to "clear" this cache?

Clear all, close all <g>...

The issue is that the WinInet runs its request on separate threads that never shut down. Those threads just sit and wait for new requests. I wasn't aware that the timeouts don't get set on a per instance basis - I have to check that out again, but if it doesn't work it surely is something that happens inside of WinInet.

The good thing is that because this works this way you can keep Cookies between requests. I suspect CLEAR DLLS will do the trick too...

+++ Rick ---