>Yes it does need to register the dll in the client, that's why I started this thread, but I think that must be some way to make it easy.
>thank you anyway
I could imagine a workaround, where you instantiate a local VFP COM object (as a wrapper), which in turn instantiates the DCOM using CREATEOBJECTEX() function and returns the object reference to VB, but that will require even more work. :)
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison