OOo Off the Wall: Fielding Questions, Part 4 - Mail Merges
Version 2.0 assumes that most users don't need anything other than the wizard. If you want to do anything except the merges included in the wizard, you need to add the tool to the menu. You can make this addition from Tools > Customize > Menu. Select the Tool menu from the drop-down list at the top of the page and then select the Add > Documents > Mail Merge > Add.
If you want to position the tool, use the up and down arrows on the Tools > Customize > Menu. Placing it above the Mail Merge Wizard is a useful place for it.
When you are ready to run the mail merge, follow these steps:
1. If you are going to print to files, place the source document in a separate folder. All the target documents go into the same folder, making them easier to find later.
2. Select Tools > Mail Merge. The Mail Merge screen opens.
3. Choose the source document from which to create the output documents. You can choose the current document or a template, that is, another source document.
After you choose, select the OK button to continue. The Mail Merge screen opens. Essentially, this screen shows the data source window on the top and printing options on the bottom.
4. In the data source window, select the database, the table and the database fields to use. Remember that for spreadsheets, the table is the sheet and the database fields are the columns. Similarly, for Mozilla address books, the table is the Named address book and the database fields are the columns.
You can open a different data source from the one you used to design the source documents. However, in order for you to use all the fields, the data source must have all the fields that you added to the labels.
5. Select the records to print. Do one of the following:
Select Records > All to print an envelope for each record.
From the data source screen, select the records to add to the labels. For each record, select its row header. Press the Shift key to select all records between two that you select or the Ctrl key to select multiple records. Selected records have a checkmark in their row header. When you have selected at least one record, Record > Selected Records becomes available. Select it.
Select Records > From to end a range of records that you want to print. To see what number each record has, look at the bottom of the data source table.
6. Select the output. You can choose either Printer or File. Note that the File option produces a Writer file, not a postscript file. One file is produced for each record.
7. If you want the output to be printed as series of single print jobs, select the Single print jobs box. This option is useful when printing to a shared printer. Merge documents are likely to be large, and single print jobs give others a chance to print between your jobs.
8. If you are printing to a file, either enter the directory for the file in the Path field or use the browsing button at the end of the field to locate the directory in a file manager.
9. If you are printing to file, choose how files should be named. Choices are:
Database setting: files take their name from a database field. If one of the fields is a company or individual's name, this might be the best option.
Manual setting: files begin with a base name that you enter, followed by a number corresponding to the record's position in the data source.
10. Select the OK button to print the individual copies of the merge document. If you print to a file, you can print each individual file later.
-- Bruce Byfield (nanday)
Fast/Flexible Linux OS Recovery
On Demand Now
In this live one-hour webinar, learn how to enhance your existing backup strategies for complete disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible full-system recovery solution for UNIX and Linux systems.
Join Linux Journal's Shawn Powers and David Huffman, President/CEO, Storix, Inc.
Free to Linux Journal readers.Register Now!
|Working with Command Arguments||May 28, 2016|
|Secure Desktops with Qubes: Installation||May 28, 2016|
|CentOS 6.8 Released||May 27, 2016|
|Secure Desktops with Qubes: Introduction||May 27, 2016|
|Chris Birchall's Re-Engineering Legacy Software (Manning Publications)||May 26, 2016|
|ServersCheck's Thermal Imaging Camera Sensor||May 25, 2016|
- Secure Desktops with Qubes: Introduction
- Secure Desktops with Qubes: Installation
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Working with Command Arguments
- CentOS 6.8 Released
- The Italian Army Switches to LibreOffice
- Linux Mint 18
- ServersCheck's Thermal Imaging Camera Sensor
- Chris Birchall's Re-Engineering Legacy Software (Manning Publications)
- Petros Koutoupis' RapidDisk
Until recently, IBM’s Power Platform was looked upon as being the system that hosted IBM’s flavor of UNIX and proprietary operating system called IBM i. These servers often are found in medium-size businesses running ERP, CRM and financials for on-premise customers. By enabling the Power platform to run the Linux OS, IBM now has positioned Power to be the platform of choice for those already running Linux that are facing scalability issues, especially customers looking at analytics, big data or cloud computing.
￼Running Linux on IBM’s Power hardware offers some obvious benefits, including improved processing speed and memory bandwidth, inherent security, and simpler deployment and management. But if you look beyond the impressive architecture, you’ll also find an open ecosystem that has given rise to a strong, innovative community, as well as an inventory of system and network management applications that really help leverage the benefits offered by running Linux on Power.Get the Guide