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


Hi all,

Sorry for the subject being confusing, but that's the best way I could
describe it.

I'm working with Avery 5384 Name Badge labels. These has six spots per page. 

I set up a layout in the upper left-hand "label", and then clicked
synchronize to make sure all the labels contained the same layout. 

Since I have 150 records, I expected to create 25 pages (6 unique labels per
page). However, when I complete the mail merge, I get 150 pages (one
duplicate label in all six positions).

I'm sure it's something really simple I'm overlooking here as this is my
first time venturing into making labels from a database.

Here's a link to the .odt file, though I'm not sure if looking at it will
help.
ReunionBadgesLayout.odt
<https://www.dropbox.com/s/th3bs3s0183gc3h/ReunionBadgesLayout.odt>  





--
View this message in context: 
http://nabble.documentfoundation.org/Label-mail-merge-producing-one-page-per-record-not-six-records-per-page-tp4011700.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+help@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.