<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Melton, Beth</title>	<link>http://tc.eserver.org/authors/Melton,_Beth</link>
	<description>A bibliography of works by Melton, Beth in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Melton, Beth</title>
		<link>http://tc.eserver.org/dir/Melton,_Beth</link>
	</image>
	<item>
		<title>Creating a Mail Merge Data Source</title>
		<link>http://tc.eserver.org/27195.html</link>
		<guid>http://tc.eserver.org/27195.html</guid>
		<description>Microsoft Word supports many file formats which can be used as a Data Source for a mail merge. This article covers specifications and frequently asked questions on the most commonly used Data Sources, along with how to set up a Data Source in Word.</description>
	</item>
	<item>
		<title>How to Create a Mail Merge</title>
		<link>http://tc.eserver.org/27194.html</link>
		<guid>http://tc.eserver.org/27194.html</guid>
		<description>Mail merge is for simplifying repetitive documents and tasks. Mail merge can be used for creating many documents at once that contain identical formatting, layout, text, graphics, etc., and where only certain portions of each document varies. Mail merge is also used for generating mailing labels, envelopes, address lists, personalised training handouts, etc. As well as hard copy mailshots, it can be used to generate multiple emails and electronic faxes. And it can even be used to create a &apos;friendly&apos; front-end to spreadsheet or database information.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Melton,_Beth.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>