You can overcome some of this by building error handling into your COM objects. Put an error method that traps for OLE errors, and fills an array property with the error information.


>Thanks Erik, I have rebuild the 2 COM (regenerated a new GUID #) and reinstalled the new COMs and it work now on all computers.
>
>
>
>I hope that MS will come with a better way to debug COM, the error message is pretty vague and doesn't mention what is wrong. I'm lucky that I have only 2 COMs, what if I had a multitudes of COMs, some dependents of others and faced this error message? What COM is causing the problem? The only way I could find to be sure that every COM are OK is to rebuild each of them in the right order.
>
>
>
>>Could this be dll version problem? It sounds like the tlb for the object does not reflect the correct available interface.

Erik Moore
Clientelligence