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)
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|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader 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