On 2025-10-24 07:02, Java Joe wrote:
Did you try changing the name before you hit Modify?
Yes, I did. As soon as I begin to change the name, the Modify button changes to Add. Hitting Add then indeed adds a new range with the desired name, while leaving the old range - as Regina's reply indicates, not a simple rename, which may have consequences. However, after changing all of the references, everything seems to work OK. But as Johnny said, it's at least a step (or so) more than optimal.
In Define Ranges dialog, I think it works if you select the desired range, modify the name in the "Name" field, then click Modify.
I should have mentioned, this is version 25.2.5.2. [I don't believe there is any difference between 25.2.5 and 25.2.6 in this regard.] I checked the Help and Calc Guide to help understand this behavior, but could not find the topic in either source. This behavior - "Modify" changing to "Add" as soon as there is any change in the name - suggests (to me) more than one developer thinking about how this should work, creating unresolved ambiguity. But more fundamental is the unresolved ambiguity between "Database Ranges" (named data ranges which *can* function as database tables) and "Named Ranges" (named data ranges which *cannot* function as database tables), and what is the purpose of the latter. Regina's bug report post and subsequent post were most informative, but did not answer that question (not, at least, to my poor grasp). Before I can understand what motivates the *operations* on either type of range, I think I need to answer that more fundamental question: what motivates the *definition* of two different entity types? Thanks for your reply, John -- To unsubscribe e-mail to: [email protected] Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/users/ Privacy Policy: https://www.documentfoundation.org/privacy
