https://bugs.documentfoundation.org/show_bug.cgi?id=141495
--- Comment #13 from Peter Johnson <[email protected]> --- I've tested further as follows: Confirmed with LO running on MacOS. Version: 7.2.1.2 / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 12; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Create file with EOMONTH function, save as xlsx, open in Excel 16.53 on MacOS. Cell with EOMONTH function shows #NAME? and string as I reported on 7/9/21. HOWEVER... with LO running on Windows. Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded Create file with EOMONTH function, save as xlsx (in Windows), copy to Mac system and open in Excel 16.53 on MacOS. The function shows correctly. I have confirmed this further with a larger xlsx file with many EOMONTH functions. If I open the file in LO/MacOS, edit and save, it is corrupted. The 'getEOMonth' etc string is visible in the formulae in LO/Win (but not in LO/MacOS); the cells show #NAME?. If I save the file as ODS in LO/MacOS, open the ODS version in LO/Win and then re-save as xlsx, the errors are not present. Conclusion: the LO version for MacOS only has this fault. That's borne out in raal's comment 12 - OS was Linux. -- You are receiving this mail because: You are the assignee for the bug.
