Thanks Tim! Now I have a hope ))
Could I reach Tim Golden somehow?
On Wed, Apr 15, 2020 at 10:09 PM Tim Roberts wrote:
> Nikita Lepetukhin wrote:
> > ok, I will report a bug. But to be honest I'm trying to find the
> > solution.
> > Do I understand right that currently there is no way to pass
>
ok, I will report a bug. But to be honest I'm trying to find the solution.
Do I understand right that currently there is no way to pass VT_DECIMAL
variant from python to com?
On Wed, Apr 15, 2020 at 9:05 PM Tim Roberts wrote:
> Nikita Lepetukhin wrote:
> >
> > Tim, thanks for replying!
> >
> >
>
Nikita Lepetukhin wrote:
ok, I will report a bug. But to be honest I'm trying to find the
solution.
Do I understand right that currently there is no way to pass
VT_DECIMAL variant from python to com?
Oh, it is possible; the library does many automatic conversions, but
it's possible to do it b
Nikita Lepetukhin wrote:
Tim, thanks for replying!
VT_CY number doesn’t fit the precision I need (16 digits to the right
of the decimal point). It has only 4 digits according to this description:
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-oaut/5a2b34c4-d109-438e-9ec8-84
Tim, thanks for replying!
VT_CY number doesn’t fit the precision I need (16 digits to the right of
the decimal point). It has only 4 digits according to this description:
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-oaut/5a2b34c4-d109-438e-9ec8-84816d8de40d
The decimal (VT_D
Tim, thanks for replying!
VT_CY number doesn’t fit the precision I need (16 digits to the right of
the decimal point). It has only 4 digits according to this description:
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-oaut/5a2b34c4-d109-438e-9ec8-84816d8de40d
The decimal (VT_D