OOo Off the Wall: Fielding Questions, Part 4 - Mail Merges
Writer includes separate tools for designing business cards, labels and envelopes. These tools include functions that make doing a mail merge easier and offer a specialized set of options. However, Writer also includes a generic mail merge tool that can be used for other purposes. In fact, many users prefer to use it instead of the envelope tool. Because the generic tool can be set to use different envelope sizes, it is at least an adequate substitute and many feel it is far less confusing to use.
Whatever your purpose, to design a generic mail merge source document:
1. Format and write the source document.
2. When ready to add the fields, do one of the following:
Select View > Data sources or press the F4 key. The data source window opens. If the window blocks part of the source document that you need to see, select the Stick icon to dock it to the upper portion of the editing window.
Select Insert > Fields > Other > Database > Mail merge fields.
3. Place the mouse cursor where you want the first field to go.
4. In the data source window or on the Database tab of the Fields screen, select the database and the table to use. Remember that for spreadsheets the table is the sheet. Similarly, for Mozilla address books, the table is the Named address book [x-ref].
5. Expand the tree view of the data source so that the individual fields are visible.
6. Select the field you want to add to the source document. A field is a column, regardless of what type of data source.
7. Drag the field into the source document with the mouse. A placeholder field is created with the name of the field inside it.
8. After the last field in a consecutive set--for example, after the last line of an address--add a field from the Database tab of Insert > Fields > Others to set the record in the database to be used next. In most cases, you probably want Next Record. (See below for more details.)
No matter which Database field you choose, notice that it is visible only as a gray background. In most cases, it contains no information, because it is simply an indicator and holds no specific data.
9. Continue steps 6-8 until all the placeholder fields are entered. At this point, you either can save the source document for future use or apply records and print it. If you save, remember that the source document needs the data source or one with the same fields in order to be used. If you are going to be using the source document frequently, you may want to save it as a template using File > Templates > Save.
Database is a tab available from Insert > Fields > Others. The fields on this tab all are related to mail merges. With the possible exception of the Database name field, they are not designed for any other use.
If you are designing labels or business cards, you can add the markers to the first label or card and then select the Synchronize button to have the fields added to all the other labels or cards. In any other mail merge, you can use the database fields to control which records are used in which order.
The Database tab fields are instructions about which record to use next. They are easy to miss on the screen, because they show up as only the gray background that indicates a field. Without them, however, a mail merge fails.
The following table describes the mail merge fields that are available:
|Field (Insert > Fields > Others > Database)||Purpose||Comments/Instructions|
|Any record||Adds the record specified to the next group of mail merge fields.||Place the marker before the group of mail merge fields it applies to. Records are numbered from the top of a data source table. If all items on the table are selected, the header row is counted, so the first record with data is 2. Use this field to control the order in which records are used in the target document. If the condition is not true, then the previous record is used instead.|
|Database name||Adds the name of a data source.|
|Mail merge fields||Adds mail merge placeholders to set up a mail merge's source document. During the merge, the placeholders are replaced by the record's entry in each field.||Fields are added at the current cursor position either by selecting the Insert button or by dragging and dropping them from the Database Selection pane into the document. When the Data Sources floating window is open, you also can drag and drop column headers into a document to create mail merge placeholders.|
|Next records||Adds a marker that signals the mail merge should add the next record to the next group of mail merge fields.||Place the marker at the end of each group of mail merge. If the marker is not added or if the condition for the field is false, then the contents of a group of mail merge fields is the same as the previous one.|
|Record number||Adds a marker that inserts the record number after each record in the target document.||Place the marker before any group of mail merge fields.|
The field is blank until the mail merge is done.
-- Bruce Byfield (nanday)
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide