Indeed useful to give more context. It is to find a fix for this bug that I have posted this message
On Thu, Nov 18, 2021, 00:35 Steven Manross <ste...@manross.net> wrote: > 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 <python-win32-bounces+steven=manross....@python.org> *On > Behalf Of *Sébastien de Menten > *Sent:* Wednesday, November 17, 2021 1:12 AM > *To:* python-win32 <python-win32@python.org> > *Subject:* [python-win32] returning #N/A to Excel via UDF > > > > 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 >
_______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
