>>>One COM object is calling another one. The method called in the 2nd COM is opening a table. When the call returns back to the 1st COM, the table opened is no longer in the scope. Is there any workaround for that?
>>
>>We've done something similar but if we need data from the table in the other com object we ask for it. The other object just serves up the data. Don't reference the table directly from the first com object, only through the other com object.
>
>One approach I am thinking of is to store the cursor result into an array. From the top COM, I would then be able to refer the 2nd COM property array.

You could pass it back as XML as well. What are you trying to accomplish?