Mike,

Is it possible that you are doing this in a loop? We had huge random problems with it and/or the O/S still thinking it was in use from a prior call into the object (even after we destroyed the object after each use). I'd even gone so far as to spawn a whole separate exe to attempt to work around the problem. It lessened the busy occurances but didn't eliminate them. We've since gone down a level and have recoded a wrapper class around the wininet.dll API functions.

>Does anyone know how to use the "InetCtls.Inet.1" object? I've got the following code:
>
>

>RELEASE oiNet
>LOCAL oiNet
>oiNet = CREATEOBJECT("InetCtls.Inet.1")
>oiNet.Protocol= 5  && icHTTPS
>oiNet.RequestTimeout = 60
>oiNet.url = "someURL.com/names.nsf?Login"
>oiNet.Execute(oiNet.url, "POST", "=&username=someuser&password=somepw&redirectto=someNewURL")
>

>
>This code sometimes works. The problem that I'm experiencing is that many times, the property oiNet.StillExecuting is .T. at the line where I CREATEOBJECT! This prevents me from continuing to do an actual Execute() method and I get the following error:
>
>

>OLE IDispatch exception code 0 from Inet: Still executing last request..
>

>
>Why is this happening? How can the Stillexecuting=.T. at the time I first create the object? All other properties are empty at that time. What would it be executing?
>
>The weird thing is that occasionally it works, but once the Stillexecuting=.T., it's very difficult for me to get it to work again.