There shouldn't be any problem with using an IP address as opposed to a name. In fact, using an IP address should always work (if the address is correct) when a name could fail because the IP address was changed and no one bothered to update the DNS server.

IAC, where does the error (if any) occur. I ran a test and it appears HTTPGet is getting the correct information as to server. Does it fail in HTTPConnect, HTTPGetEx or some other place?

As for LMHOSTS, you don't need it. LMHOSTS is the Lan Manager Hosts file. Lan Manager was the original operating system that NT was (loosely) based on. Entries in the Hosts file are usually systems outside your local network. Addresses for systems like www.levelextreme.com would be found there, if you wanted to keep this information locally which you don't.

Entries in the LMHOSTS file would consist of the Windows names of computers you see when you open Explorer. Just as the HOSTS file is used to circumvent calls to DNS (Domain Naming Service), the LMHOSTS file is used to circumvent calls to WINS (Windows Internet Naming Service).

*snip*
>In testing on my local machine (127.0.0.1) the following command works for example #1 but not #2.
>
>lcXML = oXML.LoadURL(lcURL) <-- Command I'm issuing to load my URL in
>
>1) lcURL = [http://localhost/HpTest/wc.dll?pipeline~GetMLSNames~&CID=] + lcCID <-- Works just fine!
>
>2) lcURL = [http://127.0.0.1/HpTest/wc.dll?pipeline~GetMLSNames~&CID=] + lcCID <-- Doesn't work !?!?
>
>In looking through the documentation I can see in some cases where it indicates that substituting an IP address will work and in others there is no mention that it will or will not work. So, what I'm wondering is this; does anyone know if substituting an IP for a URL will or will not work either on a local machine or on the Internet?
>