Newer Excel error types (e.g. #CALC!, #FIELD!, #BUSY, etc)

[Neil T]

I have a question regarding Excel errors.

In our application, we register a set of add-in functions using Excel-DNA. In some cases, we accept Excel errors as arguments and/or return an Excel error as the result of a function call.

This all works fine with the "classic" set of 8 Excel errors (including #GETTING_DATA). These errors, along with their internal Excel codes, are listed in the Excel-DNA class ExcelDna.Integration.ExcelError (here).

The internal codes for the classic Excel errors are mostly given by Microsoft's documentation here. (These are separate from the type codes returned by the Excel function ERROR.TYPE().)

The error codes for the new error types are listed unofficially here (not guaranteed to be identical between the various Excel APIs, but in practice I think they are). However, these errors don't behave exactly like the classic errors and it doesn't seem to be possible to read or write these errors via the C API (based on testing with a C++ add-in which doesn't use Excel-DNA).

A similar question, specifically regarding #SPILL! errors, was raised several years ago on this forum here.

These errors (especially #SPILL!) are becoming more and more prevalent with newer native Excel functions, so it's a significant gap if they can't be used with add-in functions via the C API. This is especially true if Microsoft intend to add further Excel error types, such as #PYTHON/#PYTHON! (their documentation is inconsistent on the exact text of this one).

So, in short: I am wondering whether there has been any update from Microsoft on adding support for the newer error types in the C API, or whether there is any channel of communication through which this could be raised? 

(As a side note, these errors can be detected via COM via their integer codes (yet a third numerical code for the same error!) - for example, #CALC! is -2146826238.)

[Govert van Drimmelen]

Hi Neil,

The only way I know of to provide feedback to the Excel team is through the Send a Smile / Frown feedback options inside Excel.

Updates to the C API have not been made in many years, but encouragement can't do harm :-)

-Govert

--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/0156fe2c-0d7d-4965-88c7-16607bccaeban%40googlegroups.com.

[Neil T]

Hi Govert,

Many thanks. It's at least helpful to know that this still isn't possible, and isn't likely to be in the near future.

I do wonder whether the C API has simply been "frozen in time", but I will at least attempt to ask the question!

Best wishes,

Neil

[Neil T]

Hi Govert,

Thanks for this - it's helpful at least to know that this isn't possible for the moment.

I did wonder whether Excel's C API had been "frozen in time"... hopefully not. I've sent a message but I won't hold my breath for a response!

Best wishes,

Neil

On Wednesday 19 June 2024 at 05:48:39 UTC+1 Govert van Drimmelen wrote: