>I'm wanting to build a VFP COM server and place it on a server under control of MTS. This COM server is going to open all of my databases/tables and feed the form textboxes,etc data as well as save their updates thru methods of the COM server. I intend on creating the COM server object when the application is opened. The question is whether this in-process COM server will still 'execute' on the server machine (as opposed to the clients') so that the entire databases/tables won't have to travel over the network? This COM server will eventually act as a COM object for some ASP web pages too.
>
>- A Hilton


If I understand what you want to do. Launch an application, instantiate the DLL that is running in MTS. Open forms, update tables, etc. Then, when your application terminates, destroy the MTS object.

If that's what you want to do, you aren't gaining anything by using MTS. MTS requires that you create the object, use it, and destroy it as quickly as possible. This means that you create the object over and over. Also, MTS transactions are not supported on VFP tables, so there is no gain there.