Roger Upole wrote:
> Bob Gailer wrote:
>
>> Tim Golden wrote:
>>
>>> [Bob Gailer]
>>>
>>>
OK. I don't know whether its running in a thread. I made no
changes that I'm aware of that would cause the change in
behavior. I will add the call to pythoncom.CoInitialize.
Tim Golden wrote:
>>> [Bob Gailer]
>>>
>> Yeah, but when I said it was working, it was working in the server!
>> Wednesday AM just fine. Wednesday afternoon suddenly not working fine. I
>> swear I didn't change anything!
>>
>> Is there some way my program can introspect? to see if it is in
Bob Gailer wrote:
> Tim Golden wrote:
>> [Bob Gailer]
>>
>>> OK. I don't know whether its running in a thread. I made no
>>> changes that I'm aware of that would cause the change in
>>> behavior. I will add the call to pythoncom.CoInitialize. I am
>>> not familiar with this method.
>>>
>
>> [Bob Gailer]
> Yeah, but when I said it was working, it was working in the server!
> Wednesday AM just fine. Wednesday afternoon suddenly not working fine. I
> swear I didn't change anything!
>
> Is there some way my program can introspect? to see if it is in a thread?
It's a bit clunky, but
Tim Golden wrote:
> [Bob Gailer]
>
>> OK. I don't know whether its running in a thread. I made no
>> changes that I'm aware of that would cause the change in
>> behavior. I will add the call to pythoncom.CoInitialize. I am
>> not familiar with this method.
>>
>
> This is one of those got
[Bob Gailer]
> OK. I don't know whether its running in a thread. I made no
> changes that I'm aware of that would cause the change in
> behavior. I will add the call to pythoncom.CoInitialize. I am
> not familiar with this method.
This is one of those gotcha's of Win32 COM programming;
you can
