«

Dear,

I have problems when I get the IDispatch with pythoncom.connect().
When I called the 'Excel.Application' with it, it worked. (At least I can
see the pythoncom.connect() is working for the well-designed COM like
Excel.)
When I called my COM module which was derived from IDispatch interface,
the pythoncom.connect() issued error like
com_error: (-2147221021, 'Operation unavailable', None, None).

Was my COM module badly desinged? This COM worked well with VB.
Is there anybody who solved this kind of problems?

I alse tried using the gencache.EnsureModule() after I generate a static COM
file with makepy.
In this way, I got the member function not available errors.

Thank you.

- john

"John J. Lee" <> writes:

Not another one! And there was I thinking my "J." made me safe from
namespace clashes...


> I have problems when I get the IDispatch with pythoncom.connect().
> When I called the 'Excel.Application' with it, it worked. (At least I can
> see the pythoncom.connect() is working for the well-designed COM like
> Excel.)
> When I called my COM module which was derived from IDispatch interface,
> the pythoncom.connect() issued error like
> com_error: (-2147221021, 'Operation unavailable', None, None).
[...]

Do you know about win32com.client.Dispatch and friends? Why are you
calling pythoncom.connect()?


John

"John J. Lee" wrote:
>
> "John J. Lee" <> writes:
>
> Not another one! And there was I thinking my "J." made me safe from
> namespace clashes...

Better switch to the Java approach then, Mr. com.pobox.lee.j.john ...

-Peter