Yes, this could be a solution. However, it bring thight coupling between the COM and the calling procedure, because the COM need to know how to call the calling procedure to make this work.

I'm still searching for a better solution myself on this issue. What is the ideal tool and is missing in VFP is the possibility of raising events. That way, you could raise an event when the method reached a milestone and let the calling procedure catch this event and update the user interface. I'm thinking about wrapping my VFP COM into a VB wrapper, so that the wrapper will raise events on behalf of the VFP COM.

>Perhaps you could have your DCOM object squirt back to the calling procedure a number that represents "n of total n" numbers?
>
>That way the calling procedure could update the user's form with some information.