Hi Andrew,
> Thanks for the suggestion. I've made further progress with this problem.
> First of all I need to mention that my COM component isn't written in
> C++.Net! It's just plain old C++ i think.
BTW, C++.Net is still able to create plain "old" unmanaged
COM components. You can even import the old project, if it
is a VC 6.0 project.
> I was keen on solving this problem without having to write additional
> threading code.
[quoted text clipped - 6 lines]
>
> threading("free")
That's definitely the best way.
> It has fixed my problem for the moment, but I will have to complete thorough
> testing given that i don't fully understand the changes i've made. I suppose
> i'm lucky that I have the source my my COM dll to play around with :) Thanks
> everyone.
If you take care to create the COM object in each method,
that gets called by the remoting infrastructure, you shouldn't
encounter many problems. Review the C++ code an assure that
there are no static members.
Rob