No, it is called as in the example below. I inverted the two lines of code and its now working. Thank you, Gerald.

>>Hi all,
>
>Just a shot:
>
>Dont you have to set the port BEFORE calling the connect method?
>
>
>>
>>I have a wwconnect 4.50 test executable running on our my local IIS server. The exe has a process method called: GetBills. Everything works fine. I can get results by either calling the url directly from the IE address bar or from VFP using wwHTTP.GetEx() method.
>>
>>I changed the IIS web server port from the default 80 to 5050. I can still call the process directly from IE with the port redirection:
>>

http://192.168.0.22:5050/EOSXMLServer/bin/wc.dll?XMLProcess~GetBills~&Bill=00001281 or
>>http://localhost:5050/EOSXMLServer/bin/wc.dll?XMLProcess~GetBills~&Bill=00001281
>>

>>In the VFP program however, I cannot get it to work using the nHTTPPort redirection. Am I missing something here?
>>

>>oHTTP.HTTPConnect("192.168.0.22")
>>oHTTP.nHTTPPort = 5050
>>
>>*** Initialize the variables that will be filled by HTTPGetEx
>>lcHTML=""     && Data buffer
>>lnText=0      && Size of the output to return - 0 means autosize
>>
>>*** Send the POST data and retrieve HTTP result
>>lnResult =oHTTP.HTTPGetEx("/EOSXMLServer/bin/wc.dll?XMLProcess~GetBills~&FromDate=11/05/2003",@lcHTML,@lnText)
>>

>>
>>Any help is appreciated.