At 03:22 AM 5/06/2004 +0000, you wrote:

> >
> > This situation comes out of the login dialog. You can't have
>interactive
> > stuff in an isapi at all, so you need to make LoginPrompt false.
> >
>
>Thanks! Appreciate your help. LoginPrompt was false, and I even added
>an explicit assignment:
>
>constructor TdmRegSvc.Create(AOwner: TComponent);
>begin
> inherited;
> LoadSettings;
> try
> iboConn.LoginPrompt := false;
> iboConn.Connect;
>...
>
>and still get the exception when the number of thread > 2 (i.e. 3 or
>more, 2 work fine--which if LoginPrompt wasn't set correctly, from my
>understanding, even 1 thread would not work).
>
>Suggestions?

Yes, look at my response to your second question. The qryCancelDialog
wouldn't even be created if it weren't "needed". It's trying to tell a
human that the connection can't be made, but an ISAPI can't communicate
with humans. You think it's "hanging", but really it's your application
waiting for a modal response, for which there isn't (and can't be) an
interface. It can't create "another" one because the first one hasn't been
destroyed. Catch-22.

Fix up the connection interface, make sure the TIB_Session is 0 in the
creation order, intercept connection errors in a try...except block, and
the conditions that set off the interactive "cancel login" process won't
arise.

Helen