Misy wrote:
>> If that's the only object you need to access, you should be done.
>> Go ahead and try to Dispatch it. However, if there are other
>> related classes (very likely), you'll need to import them into your
>> proxy also.
>>
>> Roger
> Hi, Roger,
>
> Well...I still fail
> If that's the only object you need to access, you should be done.
> Go ahead and try to Dispatch it. However, if there are other
> related classes (very likely), you'll need to import them into your
> proxy also.
>
> Roger
>
Hi, Roger,
Well...I still failed. I rebooted an
"Misy" wrote in message
news:loom.20110411t043551-...@post.gmane.org...
> Roger Upole hotmail.com> writes:
>>
>> You may be able to create an out of process proxy for your 32-bit app.
>> >From Administrative Tools->Component Services, navigate to
>> COM+ Applications, and then click Action->New
Roger Upole hotmail.com> writes:
>
> You may be able to create an out of process proxy for your 32-bit app.
> >From Administrative Tools->Component Services, navigate to
> COM+ Applications, and then click Action->New Application.
> Create an empty application, and then under its Components, add
Misy wrote:
> Mark Hammond gmail.com> writes:
>
>>
>> 64bit processes can't use 32bit COM objects (at least not in-proc - not
>> sure about external) and I guess your COM object is 32 bit.
>>
>> The easiest answer is probably just to install the 32bit Python and
>> 32bit pywin32 extensions - you
