Hi!

Take a look to CreateObjectEx() function in VFP. It is exactly what you need. When you use Class ID of the component, you will not require to install ANYTHING on the local workstation. When you want to use the class name, you will still require to prepare the registration of the COM component class on the local machine using DCOM or other tools. Note that on the Server machine you will require also to configure access rights to componnet using DCOM manager application, as well as compile that component into the EXE, not into DLL.

You can also register that DLL under MTS, so you will be able to use DLL instead EXE. The downside of this approach is that performance of it worse, because MTS does a lot of things, and when component is not originally designed and developed to work specially under MTS, you will not get any benefits of MTS, but lose on performance. MTS is also a kind of DCOM. MTS has its own approach and wizard to prepare client package for instaling and registering class names, though you still can use just a unique Class ID of the component for remote access through CreateObjectEX() function that does not require installation.



>Hi Guys,
>
>I am using a dll that handles the manipulation of records in a database. Can I use that dll as a server dll wherein I will only install the dll on the server and all clients will connect thru that dll on the server. Currently, I install the same dll on each work station or client.
>
>Any idea will be greatly appreciated.
>
>
>Thanks in advance.
>Mike Zapanta