> Hi all,

> I've created an EXE COM in ATL for the first time, and I'm not completely
> sure how to make use of the P/S dll.  I'm using VC7 and my configuration
is
> such:  The EXE will be on a remote machine, the client accessing it will
be
> local (presumably with the P/S DLL).  I generally use #import, but some
> things haven't made sense in my head about how this works yet.  If I
> CoCreateInstanceEx on the DLL, how does the DLL know to look at the remote
> machine?  Does the DLL have the capability to make use of the pServerInfo
> parameter?

> TIA!
> -Dale

> You will have to compile P/S DLL and register it on clients pc.
> The using dcomcnfg.exe you can specify ip address of the server.

> George.

> > Hi all,

> > I've created an EXE COM in ATL for the first time, and I'm not
completely
> > sure how to make use of the P/S dll.  I'm using VC7 and my configuration
> is
> > such:  The EXE will be on a remote machine, the client accessing it will
> be
> > local (presumably with the P/S DLL).  I generally use #import, but some
> > things haven't made sense in my head about how this works yet.  If I
> > CoCreateInstanceEx on the DLL, how does the DLL know to look at the
remote
> > machine?  Does the DLL have the capability to make use of the
pServerInfo
> > parameter?

> > TIA!
> > -Dale

> Ah, very cool, thanks.  One question about dcomcnfg and the clients...
> under location it warns that a client might override these settings.  How
> would I go about this in a client?  For instance, say I had the PS on the
> client machine but there were 5 different machines with the server EXE on
> them, and I wanted to choose at runtime (via dialog) which one to connect
> to?

> Thanks!
> -Dale

> > You will have to compile P/S DLL and register it on clients pc.
> > The using dcomcnfg.exe you can specify ip address of the server.

> > George.

> > > Hi all,

> > > I've created an EXE COM in ATL for the first time, and I'm not
> completely
> > > sure how to make use of the P/S dll.  I'm using VC7 and my
configuration
> > is
> > > such:  The EXE will be on a remote machine, the client accessing it
will
> > be
> > > local (presumably with the P/S DLL).  I generally use #import, but
some
> > > things haven't made sense in my head about how this works yet.  If I
> > > CoCreateInstanceEx on the DLL, how does the DLL know to look at the
> remote
> > > machine?  Does the DLL have the capability to make use of the
> pServerInfo
> > > parameter?

> > > TIA!
> > > -Dale

> Dale,

> If your client is running VB, use the optional second parameter to the
> CreateObject method. If it is running C++ you will have to use the
pwszName
> member of the COSERVERINFO sttucture.

> Dave Smith

> > Ah, very cool, thanks.  One question about dcomcnfg and the clients...
> > under location it warns that a client might override these settings.
How
> > would I go about this in a client?  For instance, say I had the PS on
the
> > client machine but there were 5 different machines with the server EXE
on
> > them, and I wanted to choose at runtime (via dialog) which one to
connect
> > to?

> > Thanks!
> > -Dale

> > > You will have to compile P/S DLL and register it on clients pc.
> > > The using dcomcnfg.exe you can specify ip address of the server.

> > > George.

> > > > Hi all,

> > > > I've created an EXE COM in ATL for the first time, and I'm not
> > completely
> > > > sure how to make use of the P/S dll.  I'm using VC7 and my
> configuration
> > > is
> > > > such:  The EXE will be on a remote machine, the client accessing it
> will
> > > be
> > > > local (presumably with the P/S DLL).  I generally use #import, but
> some
> > > > things haven't made sense in my head about how this works yet.  If I
> > > > CoCreateInstanceEx on the DLL, how does the DLL know to look at the
> > remote
> > > > machine?  Does the DLL have the capability to make use of the
> > pServerInfo
> > > > parameter?

> > > > TIA!
> > > > -Dale