The only way you can make a remote call to a COM DLL is if it is running on 
MTS.  Because DLL run in-process, MTS will create a surrogate process for 
it.


>From: Rowenap@w...
>Reply-To: "professional vb" <pro_vb@p...>
>To: "professional vb" <pro_vb@p...>
>Subject: [pro_vb] instantiate the DCOM_Server
>Date: Thu, 13 Jul 2000 15:4:52
>
>-----Original Message-----
>From: Ron Carran [mailto:rcarran@i...]
>Sent: 13 July 2000 02:44
>To: support@w...
>Subject: VB COM: Visual Basic 6 Programmer's Introduction to COM 2130
>
>
>Hi,
>
>I seem to have run into a (probably basic) problem while trying to
>instantiate the DCOM_Server on my server. I hope you can help.
>
>My setup is as follows:
>	Client (where VB is and where DCOM_Server.dll was compiled): Windows 98
>SE
>	Server: NT Server 4.0 (SP6a)
>	TCP/IP protocol
>
>I successfully did everything through compiling & packaging
>DCOM_Server.dll.
>I installed it on the NT server machine from package. It is running on the
>NT server. I configured DCOM with DCOMCNFG on server machine, setting all
>security as in examples.
>
>On the client machine, I ran OLE View and tried to Create Instance On the
>server and consistently got this error.
>
>
>
>What am I doing wrong? Shouldn't I be able to create this instance on
>remote
>server? I would appreciate any help you could give me.
>
>Thanks,
>Ron Carran
>