Bug 60291 - MAILMERGE: Mail Merge
Summary: MAILMERGE: Mail Merge
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.7.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-02-04 19:17 UTC by Don Nelson
Modified: 2013-05-16 03:45 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Don Nelson 2013-02-04 19:17:37 UTC
Problem description: 

Steps to reproduce:
1. New Labels: Table blank. Data Base Field Blank. Click Arrow enter each line First Name, Last Name. Next Address and so on. Options Tab: Entire Page & Synchronize Contents. New Document.
2. A Layout appears as created. Click View>Data Sources select date source. a blank Pane appears. Not the Data Base showing the Addresses.
3. Click Synchronize and the layout appears not the address labels.
4. Tools>Mail Merge Wizard: 6th step preview of Address Labels does not appear but a layout of First Name, Last Name and so on.

Current behavior: Unable to create address Lables. I have done this before using Ver. available 5/2012, I will search for a ver. available during that time and I will uninstall ver. 3.5.7.2. and install it.

NOTE: All I did was add addresses to the data base and then update the Address Labels. Been working on this for almost 2 weeks. Created the Data Base and Address Labels in May 2012. Using the same steps in Writer creating the Labels should not have been a problem.

Expected behavior: Create Address Labels.

              
Operating System: Windows 7
Version: 3.5.7.2 release
Last worked in: 3.6.5.2 release
Comment 1 Lionel Elie Mamane 2013-05-16 03:45:58 UTC
If I understand well, you are saying that this bug is fixed in 3.6.5.2, but present in older version 3.5.7.2.

Since branch 3.5.7 is closed and will not have new releases, this bug is fixed in all currently maintained branches (3.6.x, 4.0.x, 4.1.x).

Reopen if I misunderstood your report.