Interesting how HTTP gets really flakey after the first or second use of the object. But then again the WConnection documentation describes this condition so I have no complaints.<g>
I was getting bogus results after the first hit until I called HttpClose() and then recreated the object on every hit.
loHttp=.null.
release loHttp
What are you seeing exactly? I don't see any adverse effects running the sample code I posted earlier in a loop and doing 100 iterations with a single instance.
loHttp.HttpClose() is called internally in the HttpGet() call. But either way HTTP is stateless so you should always recreate the object regardless.
BTW - I'm in the process of mapping every Alcoholic related license in the State of California. I guess with 80,000 push pins on the map, I should be able to find a watering hole for your next visit without much problem.<s>
Hmmm... yeah if we can get there before they close<g>
+++ Rick ---
| Rick Strahl West Wind Technologies Where do you want to surf today? | Reader Version: 5.0 |
from Maui, Hawaii