🚀 go-pugleaf

"Gheorghe" <gmusca@dnt.ro> wrote in message 
news:438ae817@newsgroups.borland.com...
> Hi,
>
> I start IBServer as an application, and, upon starting up, use this code 
> for
> testing if server is already running:
>
>            AnsiString s = "full path to ibserver.exe";
>
>            HWND hPrevApp = FindWindow("IB_SERVER", NULL);
>            if(!hPrevApp)
>            {
>                    // start ibserver
>            }
>
> Everithing works fine, except that some customers who use Win Terminal
> Services report that code is trying to start IB even if it is already
> started. They have to shut down ibserver.exe from Task Manager and then it
> is OK.
>
> It seems that on Terminal Services, the window name is not "IB_SERVER" but
> smth. else.
> Any ideas?

The hidden window that IB uses for local connections is only available on 
the console session when running on Terminal Server.  Other sessions will 
need to connect to the server using TCP/IP and a loopback connection 
(localhost).  What you can do is connect to the server using the API to see 
if it's running.

Why not simply have IB run as a service instead?

Dan