A couple of questions?
Are both the VB and VFP in the same package?
Can you give more info on what the VFP Dll is doing?
- opening data?
- return ??? scattered name objects or custom?
- does it close it data or leave it open?
- How does the VB component create/store the VFP object?

Also, by calling SetComplete(). The VB object will be 'Deactivated' and the resource it used are gone. Then the next time you call a method on the VB it is reintialized( i think ).

Hope this helps.


>I have two Active-X DLL's. One is in VFP (data access) and the other is in VB (business rules). The VB DLL calls the VFP DLL for data, and VFP returns it in the form of an object. I have a VFP client program to test these components. It seems to work fine until I create a MTS package and put the components in them.
>
>With MTS, the same VFP client program works fine the first time a run it. When I run it a second time, it locks up when VB trys to create an instance of the VFP DLL for its first time. The VFP client program creates a VB object, calls three VB methods, and then terminates. At the end of each VB method, I do a SetComplete().
>
>I can provide more details if needed. Does anyone have a clue?
>
>Thanks!