Date: prev next · Thread: first prev next last
2024 Archives by date, by thread · List index


I have a report field that contains the following data Value

=[Ort1]&IF(NOT(ISBLANK([Ort2]));UNICHAR(13)&UNICHAR(10)&[Ort2];"")&IF(N
OT(ISBLANK([Ort3]));UNICHAR(13)&UNICHAR(10)&[Ort3];"")&IF(NOT(ISBLANK([
Staat]));UNICHAR(13)&UNICHAR(10)&[Staat];"")

As the field from the attached database query may have anything from 2
to 5 lines of text, I would like to use the function Auto Grow. There
is enough free room below the report field for the maximum line number.

'Auto Grow = Yes' is accepted and apparently saved without objection on
exiting edit. But on generating the report, the field is not autogrown.
And the setting has returned to 'Auto Grow = No'.

I want to use autogrow to optimise the use of paper space. The thought
occurs to me that, for Auto Grow to make more sense, the report
sections, in particular the Detail section, should also have
autogrow/(autoshrink?) settings.

For the moment, is there a way to Autogrow my field, or am I obliged to
set the field to the maximum available?

Cheers
Harvey



-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
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

Context


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.