Hi!

It will not be re-used if object was currently in use by another client. COM+ polling is not available for VB and VFP multi-threaded DLL components, this limitation is because of the way of the compiling of DLL COM modules in VFP and VB.

You can read more about MTS (now it is COM+ under W2K) in following article:

http://msdn.microsoft.com/library/en-us/dnfoxgen/html/mtsvfp.asp

>Thank you Vlad. Just looked at that and will try it. Suppose the COM+ object were already running in the remote machine; will a new instance be created or will the object returned point to the previously running one?
>
>Alex
>
>
>>Hi!
>>
>>Just take a look to the CreateObjectEx() function in the VFP help. When you use the class ID of the object (not the object's name) in this function, you will not require to register or install anything on the client computer (except the DCOM95 if client computer Windows system is W95).
>>
>>>We wish to make a call from VFP7 app to a method of a .NET based com+ server that is running in another machine (XP).
>>>
>>>Can anybody give me a step by step on this one, please.
>>>
>>>Thank you very much.
>>>
>>>Alex