On Mon, Dec 17, 2012 at 10:25 PM, Mark Hammond mhamm...@skippinet.com.auwrote:
The VS2008 redistributables should probably be in the same directory (ie,
msvc*90*.dll in system32) or else they might not be loaded. If you use the
depends tool from MS/sysinternals, you will see both Python
Russell Warren wrote:
Also - what is the purpose in defaulting to use both InprocServer32
and LocalServer32? Based on my problem, the default windows choice
appears to be InprocServer32. When/why would it move on to the
LocalServer32 entry? It clearly does not do it on error.
An
Russell Warren wrote:
On Mon, Dec 17, 2012 at 10:25 PM, Mark Hammond
mhamm...@skippinet.com.au mailto:mhamm...@skippinet.com.au wrote:
The VS2008 redistributables should probably be in the same
directory (ie, msvc*90*.dll in system32) or else they might not be
loaded. If you use
On 19/12/2012 2:39 AM, Russell Warren wrote:
On Mon, Dec 17, 2012 at 10:25 PM, Mark Hammond
mhamm...@skippinet.com.au mailto:mhamm...@skippinet.com.au wrote:
The VS2008 redistributables should probably be in the same directory
(ie, msvc*90*.dll in system32) or else they might not be
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 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
