On Mon, 26 Jun 2006 13:40:47 +0200, Frank G?nther <[EMAIL PROTECTED]> wrote:
>...
>
>Hi Tim,
>
>Thanks for your answer.
>Actually the same problem arises if you use VB or VBA. So the difference
>between VB and VBS is at least for this problem not to wide.
>
>
This has been nagging at me all m
On Mon, 26 Jun 2006 13:40:47 +0200, Frank G?nther <[EMAIL PROTECTED]>
>...
>
>
>
>I found a strange behaviour when I use a python-COM-Server together with
>VB.
>>>
>>>
>>>
>>> Not VB, but rather VBS. They are two rather different languages.
>>>
>>
>>
>...
>
>Hi Tim,
...
> >
> >I found a strange behaviour when I use a python-COM-Server together with
> VB.
> >
> >
>
> Not VB, but rather VBS. They are two rather different languages.
>
...
Hi Tim,
Thanks for your answer.
Actually the same problem arises if you use VB or VBA. So the difference
between VB and
On Fri, 23 Jun 2006 07:12:03 +0200, Frank G?nther <[EMAIL PROTECTED]> wrote:
>
>
>I found a strange behaviour when I use a python-COM-Server together with VB.
>
>
Not VB, but rather VBS. They are two rather different languages.
>It seems that the first argument of a COM-Method that is passed
Hi all,
I found a strange behaviour when I use a
python-COM-Server together with VB.
It seems that the first argument of a COM-Method that
is passed by a VB-variable is set to VB-Nothing after the Method call.
For example if I use the code below: After calling
testSrvObj.SetVa