Hi there,
Been debugging this issue for a bit and can’t seem to locate an easy to spot cause outside of Aspose. We’re processing a calculator for a set of data, which uses a mixture of macros and formulas to output a set of results; the VB has been externalised and works perfectly and the formulas have been calculating with no issue until now.
The one in question is in the FRACTURE_SUMMARY Worksheet of the attached Workbook, in the cells F28 and F29. F28 is a sum of the cells above it and is working as expected, and F29 MROUNDs the result to the correct factor (10 or 100 depending), and then chooses the lesser value of the output and the value of another cell.
In the case attached, the result in F28 is 1850, which should round to the nearest 100 and output 1900 to F29. This should then be compared to an external value, which is 1850, and the MIN should choose the external value. However, as you can see in the calculator (which is pulled out from the code right before result return) the value in F29 is 1800. However if you re-calculate the spreadsheet I attached you’ll see the value change to the correct output.
Wondering if this is a known issue with MIN or MROUND, or if I’m missing something obvious. Version is 1.19.3 with .NET Framework (unsure of the PROD .NET version but my local is 4.5).
Many thanks!
AT-2.zip (321.9 KB)
@sudozachcampbell,
Thank you for your query.
Please share your runnable simplified console application with us for our testing. We will reproduce the problem and provide our feedback after analysis.
@sudozachcampbell,
We evaluated your issue further. We found the calculated result of FRACTURE_SUMMARY!F29 is incorrect. We have logged a ticket with an id “CELLSNET-47244” for your issue. We will look into it soon.
Once we have an update on it, we will let you know.
Perfect, thank you for the help and for looking in to this!
Hey guys, whilst trying to make a work-around comparator for the values inside our application I noticed the actual value returned from the Cell F28 is 1849.9999999 recurring, which would round down to 1800. Would this be a possible cause? Possibly Excel have some form of conditioning for this to treat certain sig figs as the ceiling instead?
Thanks
@sudozachcampbell,
Thank you for the information. We have recorded it along with the ticket and will consider it while working on this issue.
@sudozachcampbell,
This is to inform you that we have fixed your issue now. We will soon provide you the fixed version after performing QA and incorporating other enhancements and fixes.
Fantastic news! Thank you very much
@sudozachcampbell,
You are welcome and keep in touch.
@sudozachcampbell,
Please try our latest version/fix: Aspose.Cells for .NET v20.3.3 (attached)
Your issue should be fixed in it.
Let us know your feedback.
Aspose.Cells20.3.3 For .Net2_AuthenticodeSigned.Zip (5.3 MB)
Aspose.Cells20.3.3 For .Net4.0.Zip (5.3 MB)
The issues you have found earlier (filed as CELLSNET-47244) have been fixed in Aspose.Cells for .NET v20.4. This message was posted using Bugs notification tool by Amjad_Sahi