When testing, if I deliberately feed a bogus "host" value to a TClientSocket and call Open, I (of course) get an error while trying to connect. I have a handler for "Socket.OnError", which seems to do its job ( translate the error code, etc ).
My problem is that after the initial connect error I get another error message that pops up like an exception - in other words it doesn't seem to go through my 'OnError' handler. The error message is "Windows socket error: No more results can be returned by WSALookupServiceNext (10110), on API 'ASync Lookup'"
It doesn't seem to hurt anything, other than presenting something to the user that I'd rather not present.
Any suggestions?
Thanks,
Kirk
