Hi Wei,

WinInet exist on every machine that has Internet Explorer installed. Every OS after the original Windows 95 has it installed as part of the OS, so it's a pretty safe bet. The ActiveX control also uses WinInet so you have the same issue. wwIPStuff uses WinInet, so it works in that same environment (anything above original Win95 or Win95 with IE installed).

WinHTTP works only on Windows 2000 and later which is a big drawback to its use and the main reason I have not taken to using it as it does address a couple of shortcomings in WinInet. However even WinHttp uses a number of WinInet features under the covers as well.

For widest reach and compatibility WinInet has always struck me as the best choice which is why wwHTTP uses it.

+++ Rick ---

>Thanks for the response, Rick. I think you are right, MSInet activeX control is not very good for what I need. Alex recommanded me your library here in my other post (HTTP connection), and I like it. But the concern I have with winHttp is that the application is a very old Foxpro application which is running on many pre winXP systems. I think many environments won't support winHttp. I'm looking for a quick solution at meantime. The problem I have with this ActiveX control is that how can I have it to work more reliablly. I don't want to have a lot support calls from customers after my program is on the field. If I can get it work a bit better, I'll use it for now and recommand the company to update to winHttp based interface when the old Foxpro app is upgraded.
>
>>This control is really not well suited for transactional operations. Bad design for this sort of thing...
>>
>>You can look in the library here and look for WinInet controls. There are several free examples that demonstrate how to retrieve content. You can also look into XMLHTTP or WinHTTP both of which are a more flexible and much easier to use than this activeX control.
>>
>>My company also makes a third party library that includes support for HTTP, SMTP and POP3 email. With it retrieving HTTP content is as easy as this:
>>
>>

>>loHTTP = CREATEOBJECT("wwHTTP")
>>
>>*** If you need to POST data
>>loHTTP.AddPostKey("PostKey","SomeValueToPOST")
>>
>>lcHtml = loHttp.HttpGet("http://www.west-wind.com/default.asp")
>>

>>
>>You can find it here: http://www.west-wind.com/wwipstuff.asp or in the libraries here. wwIPStuff isn't free, but it's supported and includes a ton of other stuff and functionality that the free stuff doesn't provide for advanced HTTP features (like security, downloads, streamed downloads to file etc.).
>>
>>Regards,
>>
>>+++ Rick ---
>>
>>>I wonder anyone could share some experience of using this ActiveX control in VFP. I'm trying to use this for http connection. I have a few questions.
>>>
>>>1. stateChanged. In VFP, I can only see one event - stateChanged. State 8 or 12 does not seem to always fire after I execute a Post and a response is ready. But sometimes state 8 (icResponseReceived) after I called getHeader(). When stateChange is supposed to be fired in VFP?
>>>
>>>2. hInternet. What is this property for? Initially it is set to 0. After a Post/Get, it is set to handle. However, after I cancel the request and connection, it still stays with that handle number. I am looking for a way to test to see whether the connection and request is there or not. How can I do that.
>>>
>>>3. Error. After I repeated Cancel and Post/Get, sometimes error could occur in Post/Get. How can I check to see when I can do a Post/Get?