I was just worried about getting an error. Since, it sounds like the
community has looked at it I am comfortable with the answer.
Thank you for putting my concerns to rest.
Marion
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:4757681a$1@newsgroups.borland.com...
>
> "Marion Smith" <msmith@extremeprogrammers.com> wrote in message
> news:47559a6d$1@newsgroups.borland.com...
>
>> I am having the same problem as discribed in this thread. The
>> solution appears to be to run the app outside of the IDE. This
>> doesn't seem like a solution since the error is still occuring.
>
> It is not a full blown error, and it happens internally and is handled
> privately for you anyway. The only reason you see it at all is because
> the
> IDE debugger catches all exceptions before the application code does.
>
>> I think Indy may have something to address with this.
>
> There is nothing to address. Especially since that error should not even
> be
> possible to begin with, as it is related to WSACancelBlockingCall(), which
> Indy does not use at all, and is not even support by Microsoft anymore.
>
>
> Gambit
