Reportedly, as of LO 5.1 you can create a mail merge without a Base file -
reference this: http://vmiklos.hu/blog/mail-merge-embedding.html You might
try to recreate your Certificate mail merge without the Base file being
careful to select cell formats for your data that work with Writer. (If
you have good spreadsheet skills you could likely get the job done entirely
in Calc.)
On Wed, Apr 27, 2016 at 6:18 PM, Gary Dale <garydale@torfree.net> wrote:
I've tried it with Debian/Stretch v5.1.2.2.0+ and Windows 7 v5.1.3. If I
was running anything old or unusual, I would have noted it. The document is
simple, as is the spreadsheet and the base file that connects them.
I tried changing the numbers to text but Base doesn't seem to allow that.
It's decided that the columns for age and place are decimal numbers.
So far as I can see, either the number comparisons operate differently
from the text comparisons (which the documentation doesn't mention) or the
number comparisons are broken. Normally I'd consider that unlikely, but my
past experience with printing "form letters" and labels is that these areas
don't get a lot of attention.
On 27/04/16 03:32 PM, Bruce Hohl wrote:
Can you give more details of your set-up. What is in the Writer, Calc
and / or Base components of LO.
On Wed, Apr 27, 2016 at 11:44 AM, Gary Dale <garydale@torfree.net
<mailto:garydale@torfree.net>> wrote:
I'm trying to print certificates for a group of athletes and need
to have them reflect their standing in the event. The certificate
has a number of conditional text fields, such as to translate
their gender from M/F to male/female, which are working.
However the ones that are doing numeric comparisons aren't. The
comparison always seems to return "true" so the "then" condition
is printed. For example Run Results.Race.place == 1 is the
condition but the translation text is always "first place", never
empty. Since I have 5 different conditions (first 3 positions,
participate, supported), I get a lot of text printed that shouldn't.
The slightly more complex Run Results.Race.age > 18 AND Run
Results.Race.age < 60 always prints adult. At one point I had it
print an else (senior) but that branch was never taken even when
the age was well past 60.
I've checked the Run Results.odb file (which links to a
spreadsheet) and the age & place fields are both of type decimal.
What am I doing wrong?
-- To unsubscribe e-mail to:
users+unsubscribe@global.libreoffice.org
<mailto:users%2Bunsubscribe@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
--
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
--
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
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.