Re: Mail Merge Previews Wrong



With labels, it is probably best to execute the merge to a new document and
then print that. You should make use of the mailmerge toolbar (as mentioned
in Graham's article) and not bother with the wizard which causes more
problems (such as yours) that it helps solve.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

"Marge" <Marge@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2EEC98DC-488C-4D38-B088-8DA42CA979EC@xxxxxxxxxxxxxxxx
So - when you are in the "Preview Your Labels" window it isn't "really" a
preview - it's a semi-preview and in this case it appears
wrong...therefore
you just have to "trust" and hit the PRINT choice on the "Complete the
merge"
step and assume it is going to be okay if you don't want to see the
completed
document by selecting the "Edit individual labels..." . I've just always
been
one to go ahead and print and not do the extra step, but it freaked out my
user because she only had a limited number of these kind of expensive
nametags and she/we and it originally appeared that it was going to print
all
of these duplicates.

"Doug Robbins - Word MVP" wrote:

Nothing to figure! In the first method that you describe, you have not
actually executed the merge.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

"Marge" <Marge@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:49D4096A-2C73-4C4E-BAB9-7463EB542B6D@xxxxxxxxxxxxxxxx
I had an Avery Label Template that I was using in Word to create Name
Tab
Labels (1 column, 2 to a page - small label sheets). When I merged from
Excel
(using Graham's excellent directions with the <<Next Record>> field)
and
got
to the "Preview Your Labels" point, the labels appeard wrong in that
the
first record was on label #1, the second record was on Label #2, and
then
the
second record showed again on Label #3, what was record number three
showed
on Label #4, record number three showed again on Label #5, record
number
four
showed on Label #6, etc., etc., with the records on the second label of
each
page repeating on the first label of the next page throughout the
document
as
I used the Next Recipient button to preview. When I went on to the
"complete
the Merge" step and used the "Print" feature, they continued to print
wrong,
with the repeated labels for each new sheet.

BUT - when I used the Edit the "Edit individual labels..." tool and
previewed the labels in a completed Word document, they were correct
and
printed correctly. Go figure that one???





.



Relevant Pages

  • Re: interesting article on quantum cryptography
    ... label the sorry arm and execute it in respect of its election. ...
    (sci.crypt)
  • Re: Problem writing code to go to a label after calling a procedure
    ... > where customer is the procedure and sales is a label in the customer ... > Regards Brian ... ' code you don't always want to execute ... same "Depth" down in the stack so I knew how much to offset the stack before ...
    (comp.lang.basic.visual.misc)
  • Re: Missing fields in temp tables causes errors in SQL 2000 but 2005
    ... CREATE TABLE #temp01 not null) ... select 'label B' ... print 'If not #txconnhdrinput exists, ... When I execute the stored procedure by first time, ...
    (microsoft.public.sqlserver.programming)
  • Re: Labels on multiple pages problem
    ... Did you actually execute the merge or are you just printing a preview of the ... the setup you have should produce the ... > Selected the label from the Main Document Setup menu. ... > which is the same as the bottom record of page one. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: write statement output buffer flush off on Sun
    ... > best way (in terms of efficiency) to implement alternate return ... > is to place the address of the chosen return label onto the stack ... > replacing the normal return address and then execute a normal ... Someone has to pop the arguments off the stack. ...
    (comp.lang.fortran)