add #SPILL! to ExcelError enum

95 views
Skip to first unread message

Chris

unread,
Jan 19, 2020, 2:06:30 PM1/19/20
to Excel-DNA
Govert, to support the new error related to dynamic arrays, can we get the #SPILL! error added to ExcelError enum in Excel.Integration?

It has integer value code of: -2146826243

Further info:

Govert van Drimmelen

unread,
Jan 19, 2020, 3:05:56 PM1/19/20
to exce...@googlegroups.com

Hi Chris,

 

#SPILL! errors are passed through the C API (which Excel-DNA uses) as #VALUE! errors (code 15).

So it’s not clear we can use the C API to distinguish between these two, or pass on a #SPILL! error through the ExcelError enum.

 

The COM error integer value you mention is not aligned with the C API and ExcelError enum.

 

It might be worth digging around a bit more, but it’s not as easy as adding an extra enum value.

 

-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/95c5bfab-e6a7-44f6-9589-d68515166fb5%40googlegroups.com.

Patrick O'Beirne

unread,
Jan 19, 2020, 4:10:11 PM1/19/20
to exce...@googlegroups.com
Does this list of VBA error codes help:

XlCVError [::Excel::Enum]Enum, Main

XlCVError
xlErrBlocked2047
xlErrCalc2050
xlErrConnect2046
xlErrDiv02007
xlErrField2049
xlErrGettingData2043
xlErrNA2042
xlErrName2029
xlErrNull2000
xlErrNum2036
xlErrRef2023
xlErrSpill2045
xlErrUnknown2048
xlErrValue2015


To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/009c01d5cf03%24cd7472b0%24685d5810%24%40icon.co.za.

Chris

unread,
Jan 19, 2020, 5:42:55 PM1/19/20
to Excel-DNA
Ok thanks Govert, didn't realize the C API does not distinguish it. Sounds like something Microsoft would have to update then.. or perhaps a guru like you ;)

On Sunday, January 19, 2020 at 3:05:56 PM UTC-5, Govert van Drimmelen wrote:

Hi Chris,

 

#SPILL! errors are passed through the C API (which Excel-DNA uses) as #VALUE! errors (code 15).

So it’s not clear we can use the C API to distinguish between these two, or pass on a #SPILL! error through the ExcelError enum.

 

The COM error integer value you mention is not aligned with the C API and ExcelError enum.

 

It might be worth digging around a bit more, but it’s not as easy as adding an extra enum value.

 

-Govert

 

 

 

From: exce...@googlegroups.com <exce...@googlegroups.com> On Behalf Of Chris
Sent: 19 January 2020 21:07
To: Excel-DNA <exce...@googlegroups.com>
Subject: [ExcelDna] add #SPILL! to ExcelError enum

 

Govert, to support the new error related to dynamic arrays, can we get the #SPILL! error added to ExcelError enum in Excel.Integration?

 

It has integer value code of: -2146826243

 

Further info:

--
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 exce...@googlegroups.com.

Govert van Drimmelen

unread,
Jan 20, 2020, 4:21:26 AM1/20/20
to exce...@googlegroups.com

HI Patrick,

 

I think those codes are from the Javascript integration.

The three APIs (C/SDK, COM/VBA and Javascript) don’t align exactly.

Govert van Drimmelen

unread,
Jan 20, 2020, 4:30:58 AM1/20/20
to exce...@googlegroups.com

Ah sorry – no those are indeed the VBA error codes.

Not sure that we can access the #SPILL! from the C API though.

Reply all
Reply to author
Forward
0 new messages