Nikita Lepetukhin wrote:
It's possible this is a misunderstanding in the pythoncom code. CURRENCY goes back to the days of Visual Basic 6, whereas DECIMAL is much more recent. It may be appropriate to file a bug report.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-84816d8de40dThe decimal (VT_DECIMAL) has precision up to 28 places (https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-oaut/b5493025-e447-4109-93a8-ac29c48d018d <https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-oaut/b5493025-e447-4109-93a8-ac29c48d018d>). It is exactly the same as python decimal has. They match to each other exactly and much better than VT_CY and python decimal. So maybe it wasn’t the best solution to automatically convert python decimal to VT_CY variant. Whatever.. what’s done is done.
-- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
