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


I'm investigating the feasibility of using LO Base again after a couple of years have passed. I have to say that I'm very happy with the progress that has been made on Base and reports since I last looked into it! I hope development on it continues at a steady pace. Kudos to the devs!

My first roadblock to printing the reports I need is that I can't seem to find a way to make a memo or text field with a variable height. I have several fields that contain anywhere from a few to hundreds of characters spanning several lines. If I'm forced to create a field in the report that is big enough to display all of the largest entries, I'll be needlessly blowing through reams of paper. I'm sure there must be a way to create a variable height field which will grow to fit the data that needs to be displayed and I'm just not finding it.

Can anyone shed some light on this?

Thanks!

--
______________________________
*Chad Neeper*
Senior Systems Engineer

*Level 9 Networks*
740-548-8070 (voice)
866-214-6607 (fax)

/Full LAN/WAN consulting services -- Specialized in libraries and schools/

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted

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.