>Okay,
> I'm familiar with firing VFP COM components locally. Here's my question. When I slide a new component onto an MTS box, how do the clients know that it's there? Is this some of the voodoo that MTS does? Do all client machines get an MTS.dll registered on them so that they automatically include MTS in the list of "places to look" for called DLLs?
>
> We are just getting started with this, and I'm curious how it knows....
>
>Marty
You have to put the component in an MTS package and export that package. The exporting of the package will create an executable that needs to be run on a client's PC so the package and its components are registered. The components will run on the MTS server.