Thanks Matt. I'm still hopeful there's something I can do from the python (server) side as the VB scripts are managed in somebody else's project.
Does anybody else have input on this? Is this a known issue with pyWin32 or do I need to do something differently in the server code? If a known issue, is the cause known and a fix in the works? Alternately, can somebody help me identify the issue in the pyWin32 source so I can rebuild my local copy? Thanks. - Gerry On Mon, Nov 29, 2010 at 8:19 AM, Matthias Kirst <m...@clondiag.com> wrote: > We stumbled across the same problem (10 years ago) and our solutions are: > > - use global variables > > - copy variable to another one and call COM server with this copy > > > > Hope this helps, > > Matt > > > > _______________________________________________ > python-win32 mailing list > python-win32@python.org > http://mail.python.org/mailman/listinfo/python-win32 > >
_______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
