Unable to find any combination of arguments that give a meaningful result for either function. Constantly return #VALUE!
Code inspection of GetOddfprice and GetOddfyield functions in file source/analysis/analysishelper.cxx seems to indicate that both unconditionally throw a runtime exception.
AOO Bugzilla #92177 also refers.
Steps to Reproduce:
User Profile Reset: No
Version: 188.8.131.52 (x64)
Build ID: 8349ace3c3162073abd90d81fd06dcfb6b36b994
CPU threads: 6; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win
Locale: en-GB (en_GB); UI: en-US
Seems like that since:
author Daniel Rentz <firstname.lastname@example.org> 2001-09-26 12:22:24 +0000
committer Daniel Rentz <email@example.com> 2001-09-26 12:22:24 +0000
commit 2f0d97cd957cdb3113d98cbc441a923a43367547 (patch)
parent f5b732c43a9ed9ace11412d85dacd96d849fcde1 (diff)
#87380# return error for ODDF(PRICE|YIELD) due to faulty algorithms
Eike: should we remove these functions or should we still wait for someone try to implement them?
(I found these links from MS:
Removing the functions wouldn't help anything except changing the error from #VALUE! to #NAME? ...
Keeping them has the benefit that when a document is saved as old .xls binary format then the macro class is preserved due to the implementation as Add-In and it would (continue to) work in Excel.
(In reply to Eike Rathke from comment #2)
> Removing the functions wouldn't help anything except changing the error from
> #VALUE! to #NAME? ...
Just decruftify a bit the code
> Keeping them has the benefit that when a document is saved as old .xls
> binary format then the macro class is preserved due to the implementation as
> Add-In and it would (continue to) work in Excel.
Didn't know about this part.
Ok I understand better now why this thing is still there unimplemented after so many years.
Thank you for the feedback! :-)
Both functions are in ODFF standard.