OpenOffice.org Address Books and Form Letters
Another choice for an address data source is an LDAP server. Selecting LDAP from the AutoPilot's Address Data Source window and then clicking Settings will bring up the Create Address Data Source window. Here you can specify the LDAP server's location and the user name and password required to access the server.
A documented issue with OpenOffice 1.0 is that the first connection to an LDAP server must be made as root. After this first connection is made, normal users can then access the server. I was able to connect to a test OpenLDAP server on my system, but I could not display any information from it. The OpenOffice.org web site indicates this is another known problem.
Finally, you can use dBase files as an address source. Simply pick Other from the AutoPilot's menu and select dBase as the Database type. Select the directory containing the .dbf file, and then make sure the correct filename is checked. After clicking OK, go through the field assignment procedure to map OpenOffice's address fields to the fields in the database.
One advantage of using a dBase file is you can edit the records it contains when the Data Sources window is displayed. Address books from other sources can't be edited from the Data Sources window.
OpenOffice.org does have some quirks when dealing with address books. Clicking the refresh button on the View Data Source window didn't actually update the data shown. The only way to show the updated information is to restart the application.
Another problem is the application will hang if you hide the Data Sources window while Mozilla/Netscape's address book is being viewed.
A form letter is a document containing fields populated by information from an address book. There are two ways to insert these fields into a document. One way is to position the cursor where you want the field and then click Insert -> Fields -> Other (keyboard shortcut Ctrl-F2). Click on the Database tab and select Form letter field in the Type list. In the Database Selection window pick the address book and field to insert, and then click the Insert button (see Figure 5). This will put a placeholder in your document where information from the address book will be inserted. Once you have inserted the fields that you need, click Close and continue editing your document.
The second way to insert fields is to display an address book in the Data Sources window and then drag column names from the table into your document.
After you have created and saved your form letter template, you have to generate the letters that will be sent to each addressee. These letters can be printed out, saved as individual files on your hard drive or sent as e-mail messages.
To generate form letters, click File -> Form Letter. This will bring up the Form Letter window where you can select which addressees to use (all, selected or a specific range). Choose whether the letters should be printed, saved to disk or e-mailed, and then click OK. Note that in order to send your form letters as e-mail, you must have Netscape 6.x installed. OpenOffice.org can't send form letters as e-mail using Mozilla.
OpenOffice.org offers you the ability to filter your address book data using SQL statements. Because you can create address books with custom fields, you can target form letters to specific customers based upon criteria such as a purchased product or a renewal date. You can also limit your form letter to addressees in specific area codes, zip codes or states.
To use this feature, open the Data Source Administration window (see Figure 6) by clicking Tools -> Data Sources. Select the database you wish to use, and then click on the Queries tab. Clicking on the New Queries button will bring up a SQL statement builder window (see Figure 7). This window allows you to build a query and run it to see its results. Make sure you include all the fields in your query that you will insert into your letter. Once the query works as you would like, you can save it with a descriptive name and use it again.
To insert fields from an SQL query, select the query as your database selection in the Fields dialogue (Insert -> Fields -> Other). When you generate the form letters (File -> Form Letters), select the query you wish to use from the Form Letter window instead of an address book table.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
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.Register Now!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Interview with Patrick Volkerding
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
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