Thanks for help.
But in general, why a client would not use an application pooling?
It will create as many instances as it's set in a pool size and then simply will not run the component. Is it becasue my VFP code is not written properly?

>Mark, try these articles:
>
>http://www.dotnetextreme.com/articles/ComDotNetDiff.asp
>
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cossdk/htm/pgdesigningapplications_46sz.asp
>
>http://msdn.microsoft.com/msdnmag/issues/02/02/Basics/
>
>and the articles on Craig's site
>
>http://www.craigberntson.com/articles.htm
>
>In general, getting the reference to the COM+ Context object and using its methods makes your VFP COM object COM+ compatible.
>See the samples in Craig's articles.
>
>>Right.
>>But what if I'd like to use VFP COM via COM+? What do I need to have in VFP code for that?
>>
>>>There's no COM+ involved. .NET creates class wrapper around VFP COM server so it can be used as any other .NET class.
>>>
>>>>But what I dont understand is what makes VFP code COM+ compitable?
>>>>
>>>>>Mark,
>>>>>
>>>>>Take a look at http://west-wind.com/presentations/VfpDotNetInterop/vfpDotNetInterop.htm and http://www.west-wind.com/presentations/VfpDotNetInterop/aspcominterop.asp
>>>>>
>>>>>>I am calling that component from a web service written in C# to update a few Fox tables.
>>>>>>