An application or component that uses objects provided by another component
is called a client.

Components are characterized by their location relative to clients. An
out-of-process component is an .exe file that runs in its own process, with
its own thread of execution. Communication between a client and an
out-of-process component is therefore called cross-process or out-of-process
communication.

An in-process component, such as a .dll or .ocx file, runs in the same
process as the client. It provides the fastest way of accessing objects,
because property and method calls don't have to be marshaled across process
boundaries. However, an in-process component must use the client's thread of
execution.

A Microsoft Transaction Server (MTS) component is a type of COM component
that executes in the MTS run-time environment. In addition to the COM
requirements, MTS requires that the component must be a dynamic-link library
(DLL). Components that are implemented as executable files (.exe files)
cannot execute in the MTS run-time environment. For example, if you built a
Remote Automation server executable file with Visual Basic, you must rebuild
it as a DLL in order to use it in an MTS environment.


Hope this helps - Looks like I was wrong about being able to reg a Active
EXE *.tlb in MTS 

Regards

T


-----Original Message-----
From: James Ullom [mailto:ullom@i...]
Sent: 12 October 2000 23:48
To: professional vb
Subject: [pro_vb] High Level question on MTS/COM/DCOM


In reading and trying to understand the differences of distrbiuted
computing, can someone confirm or deny my following summary of COM stuff:

ActiveX DLLs (COM): Runs on the local machine in the the application's
process space
ActiveX EXE (DCOM): Run on local or remote machines outside of the
application's process
MTS: Allows an ActiveX DLL to operate on a remote machine utilizing it's
Context Wrappers and such, plus all that transaction support.

Thanks

James Ullom