Victor Liu wrote:
Gratitude to all the work of the library. I am trying to use it to
send out some emails, but I have encountered this issue which might be
a bug. It can be represented by this minimum working example.
It might perhaps be a bug, but it is not a bug in Python. All you're
do
As best I remember, Microsoft considers the programming of Mail tasks (and most
Outlook automation) as a security risk/issue, and limits your access to certain
parts because so many people (malware writers) wrote stuff to programmatically
abuse Outlook for unsavory (Evil?!?) purposes.
However,
While I don’t have any useful suggestions here… I thought I would link the
thread I found in the xlwings github thread that the author looks to have been
working on with them already.
https://github.com/xlwings/xlwings/issues/776
HTH
Steven
From: python-win32 On
Behalf Of Sébastien de Mente
Hi guys,
Gratitude to all the work of the library. I am trying to use it to send out
some emails, but I have encountered this issue which might be a bug. It can be
represented by this minimum working example.
import win32com.client
outlook = win32com.client.Dispatch('outlook.application')
mail
I would like to return #N/A values to excel via an UDF written in python
(via xlwings)
Returning a `VARIANT(pythoncom.VT_ERROR, 2042)` from the UDF results in an
empty cell.
Is there within pywin32/pythoncom an equivalent of VBA `CVErr(xlErrNA)` ?
Sébastien
___
