About building a COM/MTS client
A PowerBuilder application can act as a client to a COM server.
The server can be built using PowerBuilder or any other COM-compliant
application development tool and it can run locally, on a remote
computer as an in-process server, or in Microsoft Transaction Server
You can use the Template Application start wizard to help
you build COM and MTS clients.
Configuring a client computer
to access a remote component
When a COM component is running on a remote computer, the
client computer needs to be able to access its methods transparently.
To do this, the client needs a local proxy DLL for the server and
it needs registry entries that identify the remote server. The client
computer must be running Windows NT 4.x, Windows
98, or Windows 95 with the DCOM update.
If the component is installed in MTS, MTS Explorer can create
an executable configuration utility to set up a client to use the
COM component. Running the executable file on the client copies
the proxy DLLs and type libraries to the client and makes registry
entries. For how to create and run the configuration utility for
a PowerBuilder COM server, see “Deploying PowerBuilder COM
objects to MTS”.
If the server is not installed in MTS, the client and proxy
files must be copied to the client and the server must be configured
to run in a surrogate process. For more information, see “Using PowerBuilder COM servers
and objects with DCOM”.
Remote server name written to registry If MTS or the COM server is moved to a different computer,
the registry entries on the client must be updated.