You are correct. If you have the source code, it is not a big deal to change
the project to an ActiveX DLL. If you don;t have the source, you will have to
contend with DCOM manually.

Clif

--- Gopalakrishnan <ntg@s...> wrote:
> hi Clifton,
> 
>     But to me, u can't use an ActiveXEXE in MTS. You can use only
> ActiveXDLLs there. please correct me if i am wrong....
> 
> Regs.
> N.T.GOPALAKRISHNAN
> 
> ----- Original Message -----
> From: "Clifton Dunaway" <csdunaway@y...>
> To: "professional vb" <pro_vb@p...>
> Sent: Tuesday, February 13, 2001 10:10 PM
> Subject: [pro_vb] Re: ActiveX.EXE running on Server opening Multiple
> sessions
> 
> 
> > I would consider using Microsoft Transaction Server for htis task. It is
> simple
> > to add a reference to teh DLL project for MTS use. This will remove all
> > problems!
> >
> > Clif
> >
> > --- Charlie Hughes <Charlie@L...> wrote:
> > > I am curious if anyone else has run into this problem.  We have an
> ActiveX
> > > EXE that runs on the server.  It is set to run as the interactive user
> in
> > > DCOM because we want all the clients to use the same instance of this
> > > ActiveX exe.  Most of the time it runs fine but every onece in a while
> > > each client will trigger their own instance of this exe and then the
> > > system crashes.  Does anyone know how to keep this from happening?  We
> are
> > > not sure if it is a DCOM issue or an NT issue or even a hardware issue.
> > > Thanks in advance for any suggestions.
> > >
>