Quoting Tim Roberts t...@probo.com:
There is no danger in redoing a registration that has already been
done. All it does is add some registry keys. Might as well just do it
every time. Add /s if you don't want to see the dialog box.
Alternatively, assuming you are running a 64-bit Python,
I'm having a really difficult time trying to get a simple COM server demo
working with win32com. No matter what I do I'm getting an automation error
(The specified module could not be found.) when I try and create the
object from VBA with CreateObject().
The latest COM server I'm trying to create
Update - it seems to be the pythoncom27.dll somehow. I tried deleting the
InprocServer32 key and my com server works now.
I see that I can dodge this issue by specifying _reg_clsctx_ =
pythoncom.CLSCTX_LOCAL_SERVER, but I'm concerned about what the problem
could be with pythoncom27.dll and
On 12/16/2012 6:17 PM, Mark Hammond wrote:
I'm the vendor of the object :) As I mentioned, I just created this
small test app which reproduces the issue having just those 3 simple
methods. However, I'm not able to talk to it via Python.
Is the source to this available?
Yes, its just a
Dave sent me the source via email.
The root problem is that the MFC project is not supporting the
GetTypeInfo() and associated calls, and TBH I'm not sure how hard it
would be to make it support that. The end result is that the makepy
support for the object isn't being used as pywin32 can't
On 12/17/2012 8:25 PM, Mark Hammond wrote:
Dave sent me the source via email.
The root problem is that the MFC project is not supporting the
GetTypeInfo() and associated calls, and TBH I'm not sure how hard it
would be to make it support that. The end result is that the makepy
support for
On 18/12/2012 6:27 AM, Russell Warren wrote:
Update - it seems to be the pythoncom27.dll somehow. I tried deleting
the InprocServer32 key and my com server works now.
Assuming you installed Python for all users, the pythoncom27.dll being
used should be the one in the system32 directory, and
