And let's not forget that even though you can register a VFP component in MTS, it will NOT be multi-use. Simultaneous calls to a component method will queue up, severely limiting scalability. This problem is supposedly going to be fixed, but until it is I wouldn't recommend using VFP components in MTS. As Craig said, there just isn't any real gain to it.
>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.
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
