Hrm...ok, well http://123.123.123.123/ was a white lie in that it's much simpler than the real URL, but I didn't realize that INetLibURLCrack was so weak...
I'm really doing things like: http://123.123.123.123/a?u=whoever&p=pass&m=1&n=2 ... etc etc ... Can INetLib not always successfully handle this?!?! On Tue, 18 Jul 2000, Fitzpatrick, Joe wrote: > In this particular case I would say the culprit is INetLibURLCrack, which is > being called indirectly on your behalf. If you substitute a non-ambiguous > URL for the one you are using: > > ex. http://123.123.123.123/index.html > > I would expect the error to go away. As for repeat requests, there are a > number of gotchas there as well. Brute force (initializing and cleaning up > the lib around every transaction) works well, but can be avoided for simple > GETs. > > Good Luck, > -jjf -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
