🚀 go-pugleaf

Bob Gonder wrote:

> You have an exe, that when launched as instance 1 (i1), it does what?
> Does it behave as an application, or a COM Server, or a self-contained
> application that uses COM services?

I have an EXE that can be launched by the user and then behaves like a
normal application. It can also act as a COM server and can be launched
by the system to support COM requests.

My problem is that I can't have the user launched application instance
trying to be a COM server. I've stopped that from happening but I'm
left with the problem that I don't know how to tell the OS to load
another instance to act as a server.

There is no problem if the EXE hasn't been launched by the user. With
multiple COM clients each client starts its own instance of the server.
Obviously in this case /something/ indicates that the existing
instances are 'spoken for' and that a new instance is required.

> When the exe starts, it checks, and if
> it is (i1), it becomes a Com Server, and relaunches itself (i2) to be
> the application.  Then if the user launches again, (i3) sees the flag
> and becomes an application too.

That's exactly what we want to do but we don't know how to code the
logic that prevents an EXE from being a COM server. It is probably just
a hole in the documentation but having created a COM server we need to
know what to call in order to disable it.
-- 
Andrue Cope [TeamB]
[Bicester, Uk]
http://info.borland.com/newsgroups/guide.html