I have not seen the latest LO versions but the last version I tested this on failed my test.
The problem is that cells that contain or are dependent on cells that contain the function call
CELL("filename") do not get recalculated automatically based on performance of "Save as …" even
though that action changes what that function is supposed to return.
Has this been corrected in or before the newest version? Is there even a confirmed bug report
regarding this behavior? It makes the function call rather meaningless.
A _partial_ work around is to use the following construct:
IF(COUNT(range)>-1,CELL("filename"),"")
but even that fails until something changes within the referenced range (e.g. enter zero and undo
the entry).
All versions of the open office line (OOo, AOO, LO, and now AnOo {Android}) that I've seen share
this flaw. I hope a universal fix for this will be created by somebody and that it will be shared
among the various projects.
--
Jim
"A man convinced against his will
is of the same opinion still."
— Unknown
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] Calc bug query · James E Lang
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.