Do you find the Support WebCast transcripts helpful?
Let us know!

Note This document is based on the original spoken Support WebCast transcript. It has been edited for clarity.

Richard Roddy: Thank you. Our topic today is Mail Merge in Microsoft® Word 2002, and we'll be going through the Mail Merge process as it applies to Word 2002. We will be skimming over the Mail Merge process a little bit, so if you would like to get more details regarding exactly what a Mail Merge is or possibly some more detail regarding some of the more intermediate and advanced features of Word's Mail Merge, you may want to take a look at the previous WebCasts for Microsoft Word 2002 Basic and Intermediate Mail Merge.

There are a number of screen shots and dialog boxes in the PowerPoint® slides, which may appear small during the WebCast, but if you download the slides, you can view them at a very readable size. Now we'll move to our second slide, which are our objectives.

The objectives today are to show the new Mail Merge process in Word 2002, highlighting the differences between it and prior versions of Word, specifically Word 2000. We will also have a very short overview of OLE DB as the new default data access method for Mail Merge in Word 2002.

On our next slide, slide 3, we have the three basic parts of a Mail Merge. We have our data source, which is our list of addresses of our recipients and that sort of thing that we're going to be sending our Mail Merge to. The main document is the layout of our letter or whatever else that we're going to send. Then we have the results of putting those two together.

On the next slide, slide 4, we have a look at the Word 2002 Mail Merge Helper. It split this process up into the three main parts of the merge: the main document, the data source, and then merging the data with the document. Of course, even though it was split into three parts, the process actually took quite a bit more then three steps.

On to the next slide, slide 5. The main thing now is that in Word 2002, one of the main goals of changing the process was to make it a lot clearer than it was previously. Building on the new task pane interface that has been introduced in the Office XP applications, Mail Merge in Word uses the wizard in the task pane. This wizard is visible during the entire Mail Merge process and gives you several pieces of information at each step: the title of the current step, options that are available for that step, actions that you can perform during that step, a description of the step, and then navigation forward and back through the wizard.

On the next slide, slide 6, we can see the six steps of the Mail Merge Wizard. We'll go through each of these steps as we step through a sample Mail Merge scenario.

On slide 7, we get to step 1, which is to select the document type. The document type can be letters, e-mail messages, faxes, envelopes, labels, and a directory. Directory used to be known as catalog in prior versions. The one thing that a number of people may not see when they get to this step, is faxes available as a choice, and that is largely dependent on the fax software installed on the machine and whether it can interface with Microsoft Outlook®.

On the next slide, slide 8, we get to start the document. Here we have options to use the current document, which means whatever document you've currently got up on screen; start from a template, if you've got a specific letter template or something like that that you'd like to start from; or start from an existing document, which is a new option from previous versions.

On the next slide, slide 9, we get to step 3, which is selecting our recipients. We have the choice of using an existing list, which can be just about any type of data source, thanks to the multitude of data sources that we now have support for through OLE DB, although for most people the most commonly used data sources are Access databases, Excel workbooks, and Word documents. We can use our Outlook Contacts and we can type a new list.

On the next slide, slide 10, which is a continuation of step 3, we have greatly improved using Outlook as the data source. Word, by default, now uses a standard set of field names, which are the same as the field names used in Outlook, so mapping of the field names between the two applications is automatic. When a merge is initiated from Word, we now have more support for a larger number of Outlook contact fields than we had in the past, although to have the most fields available, we would still initiate the merge from Outlook. In the filtering of the recipient list, we also now have an operator called contained, which allows us to easily filter on the contents of the category fields in our Outlook Contacts.

The next slide, slide 11, also continues step 3, and it is a type of new list dialog box. Using this dialog box, we can create a new recipient list with any set of fields we want, although it starts up with the standard set of fields. We can just change those by clicking Customize and rearranging, removing certain fields, and adding new fields. This is called the Office address list and it saves as an MDB file, or pretty much a modified Access format, containing tables with predefined names. It is handled by the Mail Merge feature as a special case type of file. For example, what that means, in this case, is you can edit the Office address list MDB file from within the Word Merge wizard, but you can't edit Access MDB files from within the wizard.

Continuing step 3 on the next slide, slide 12, Word 2002 introduces a new Mail Merge Recipients dialog box. This dialog box provides an environment for viewing, filtering, sorting, and editing the recipients of the current data source, without having to access the application that created the data. The Mail Merge Recipients dialog box makes it simple for us to sort the items in the list, which is very useful if you want to see the items in alphabetical or numerical order. All we have to do to sort is click the column heading of the item we want to sort by. So if we wanted to display the list alphabetically by last name, we would just click the last name column heading.

We can also filter items in the list, which is useful if the list contains records that you know you don't want to see or include in the merge. Once you've filtered the list, you can use the check boxes to include or exclude records, as described in the previous section. We click the arrow next to the column field heading of an item if we want to filter by it.

Now we move on to step 4 on slide 13, which is writing or arranging our main document. This is where we actually write the letter that our data will be merged into. Word 2002 introduces a few time savers for us in this step. We're now able to quickly and easily insert commonly used pieces of information into our main documents that were more difficult to insert in past versions. With just a couple of clicks, we can now add a full address block, greeting line, electronic postage, or postal barcode, compared to having to manually construct most of these in prior versions of Word.

On our next slide, slide 14, we take a look at the Insert Address Block dialog box. Word makes this a lot easier now. We just specify the format we want our recipient's name to show up in by choosing different options in this dialog, whether or not to insert the company name, and whether or not we should include the country or region in the address.

The Insert Address Block dialog box uses intelligent name and address fields to provide a way to insert recipient information into Mail Merge documents, so that the layout of the information adapts to the content. These intelligent fields are designed to produce sensible output in spite of differences in the information in each contact record or whatever name was used for the field in the data source. Also, in previous Word versions, we would have to insert a number of fields in a specific order to represent an address block, and often we'd end up with mixed results when doing this. Using the intelligent name and address fields helps us deliver consistent results.

On the next slide, slide 15, we see where we can also insert a greeting line with a specific format. You'll note here that this dialog allows us to select how our greeting will look when we have a valid recipient name, and also what we would like to insert, such as "Dear Sir or Madam," when we don't have a valid recipient name. The address block and greeting line fields look like merge fields within the document, except that the chevrons (little arrow signs on either end of them) are doubled to indicate a special merge field.

As we move to the next slide, slide 16, we get our Match Fields dialog box. If this dialog box appears on its own when we're working on a merge, it means that Word may have been unable to find some of the information it needs for the address block. Additionally, we can also manually display the Match Fields dialog box from either the Address Block, Greeting Line, or More Items dialog boxes by clicking the Match Fields buttons.

Word uses field matching to allow us to attach different data sources to a main document without having to change the field name. When a data source is selected, Word attempts to map the fields in the data source to a list of standard merge fields to improve the functionality of templates and insert buttons, such as the Insert Address Block and Greeting Line.

The following data sources most likely will map correctly without any need to match fields because they mainly use predefined field names that already match the standard field names. This would be the Outlook Contacts, Office address lists, which are created by doing Create New List in step 3, Word 2000 files that use the default field names that Word 2000 would set up, and Publisher 2000 address lists that use the default field names.

The Match Fields dialog box has two categories of fields. It has required information and optional information. The required information section contains fields whose presence is required for successful use of address blocks and greeting lines. The optional information section creates fields that are not needed for address blocks or greeting lines to function, although mapping the optional fields may cause them to work better for you.

Next, we'll move on to step 5 on the next slide, slide 17, which is to preview the merge results. During this step we can make changes to the main letter, which will impact all of the resulting letters. We can also exclude the current recipient that we're viewing from the merge just by clicking Exclude this recipient. If we want, we can also print the individual merge results at this step by just clicking Print while we have that merged record previewed.

Next, we have step 6 on slide 18, which is the actual conclusion of the merge. It is at this point that we will send the merge results either to the printer or to a new document. To print all the results, we just click Print in the Mail Merge Wizard and then specify whether to merge all of our records or specify a specific numbered range of records to print. By clicking Edit individual letters, we merge the result to a new document that we can then edit and change individual letters in before we print it or save it. We can also specify to merge only a specific range of records when we merge to a new document, just like the choice that we got when merging to the printer.

On the next slide, slide 19, we'll start getting into the differences that there are in some of the steps for other document types. The main types that we'll see differences for will be e-mail messages, envelopes, and labels.

We'll first look at the differences in e-mail messages, on the next slide, slide 20. We see the heading that we have here is Message options. When we get to step 6 and perform the actual merge to e-mail, we get a dialog like the one shown here for the message options. In the dialog, we will select which merge field contains the e-mail addresses that we want to send our results to, we'll specify a subject line for the message, the format we are going to merge to, and then which records we want to merge.

An important note here is that when merging e-mail, if we chose plain text for our format and are using Outlook as the MAPI e-mail client, we will get prompted by Outlook security features prior to sending each message. So if we're merging 50 recipients, we would get 50 prompts making sure that we want to send each message. The workaround is to use HTML as the mail format or to set the default mail client as Outlook Express, at least for the duration of the merge. This is an unfortunate limitation that was encountered in getting merge to e-mail to work with the new Outlook security model. They really wanted to make it work for both plain text and HTML, but time and technical limitations caused us to end up with the current limitation.

On the next slide, slide 21, we'll look at the differences that we have when choosing envelopes as the document type. At step 2, which is shown here, when we select the starting document, we have Change document layout instead of Start from a template. We also have the choice to set our envelope options. If we click Envelope options in this step, we'll get the dialog box shown on the next slide, slide 22, which is Word's standard Envelope Options dialog box.

In the dialog box we have two tabs. One for Envelope Options, which contains the size, fonts, and text positioning of the addresses, but because we're working on a Mail Merge envelope, we can easily change the fonts and address positions later in the process. We don't have to change them now. We could go ahead and change them now because it's a little bit easier to change it here than it is to change it later on. We also have a Printing Options tab, which is where we modify how Word thinks the envelopes should feed for your specific printer, as well as what tray they should be pulled from.

On the next slide, slide 23, we get into the differences in the process that creating a labels document causes. In step 2 here, we have options very similar to the envelopes document type. We have Change document layout in place of Start from a template, and we also get a choice to set our label options.

When we click Label options, we see the dialog box shown on this slide, and in the dialog box we choose what type of printer we have and then we specify the label product that we're using. In Word 2002, we have a much larger variety of label products that are listed here, multiple manufactures of labels, as well as more of their products. We can also specify custom label settings if we don't find a match for our product here.

On the next slide, slide 24, we have step 4 of working with labels. In this step, we now have an option to replicate the information on the first label on the page to the rest of the labels. This is a great addition from prior versions. When creating the labels in prior versions, if we wanted to modify our merge labels after creating the main label document, we had to manually modify all of the individual labels. So if we were working on a label page that had anywhere from 10 to 20 labels on it, you could see how that really was a bit of an annoyance.

Now we just modify the first label on the page and then we click Update all labels, and presto, all the information on our first label is now replicated to the rest of the labels on the page. Word automatically puts in the next record fields that are necessary for us to properly merge, and it puts a different recipient on each label.

As we move onto the next slide, slide 25, I can already hear some of the folks out there who are very familiar with doing Mail Merges in Word saying, "This wizard interface is just going to slow me down." Well, that may be true, but for those users, we have a Mail Merge toolbar that has the whole process laid out and will allow you to skip the wizard. Note that the toolbar is no longer displayed automatically when creating a Mail Merge, as in past versions. So we need to display it by clicking View and pointing to Toolbars, and it will also stay up as one of your toolbars as long as you leave it turned on. It will not close automatically either.

As we look at this toolbar, we have the following buttons and functions on it. The first one is Main Document Setup, which is equivalent to step 1 from the wizard and also gives us an option to remove all merge information from our document and restore it to a normal Word document.

The next button we have is the Open Data Source button, which is the same as if we clicked Browse in step 3 of the Mail Merge Wizard to open an existing data source. We can only use an existing data source when we do it that way. We have to use step 3 of the wizard if we want to use our Outlook Contacts.

The next button is Mail Merge Recipients, which displays the recipients dialog box. If no data source is open, this button is disabled. Then we have Insert Address Block, Insert Greeting Line, and Insert Merge Field; this Insert Merge Field button is the same as the More Items button in step 4 of the wizard. Then we have Insert Word Field, which works the same as in prior versions of Word to put in ask, fill in, next record, and fields such as those. Then we have View Merged Data, which has the same functionality as in previous versions. Then Highlight Merge Fields, which highlights all of the merge fields in the document, which makes it a whole lot easier to see where the merge fields are if we're previewing and not 100 percent sure if some of the text we're looking at is text that is fixed or text that's coming in from the data source. Then we have the Match Fields button, which displays the Match Fields dialog box. We have the button for Propagate Label, which updates the changes from the first label to all other labels on the page just like the Update all labels button in step 4 of the wizard. We have our Record Navigation buttons, which are used to step through or display specific recipients when we're previewing the merge results, and unless the data source is open, these are disabled. We have a button for Find Record, which has the same functionality as previous versions of Word; it allows us to quickly pull up specific records using search criteria. Then we have Check for Errors, and again, it has the same functionality as past versions; this primarily just checks to make sure there are no merge fields in our document that don't exist in our data source. Then we have Merge to New Document, Merge to Printer, Merge to E-mail, and Merge to Fax. These buttons do the same operations as found in step 6 of the wizard for the appropriate document type. They, again, will be disabled when appropriate.

On the next slide, slide 26, we talk about some new field switches that have been added. In earlier versions of Word, many of our merge documents contained double spaces around missing fields. For instance, if we had a field such as Title for Mr. <first name> <last name>, and we had spaces in between them, we would get as our result, Mr. Jones (with two spaces between Mr. and Jones), if we had a record that was missing a first name. Word 2002 supports two new switches on the merge field to specify text that is printed before or after the data of the field, but only if that field contains data. These are \b and \f.

The \b switch specifies the text to be inserted before the merge field if the result of the merge field is not blank. The \f switch specifies the text to be inserted after the merge field if the result of the merge field is not blank.

Then we have the \m switch. This switch is used to specify that the field in this case is a mapped field. Any merge field entered into the document using a standard merge field contains this switch. Usually, these fields are entered from the Insert Merge Field dialog box using the fields shown with the Address fields option selected. A result in this situation is a merge field such as merge field, the name of the field, first name, and then a space, and a \m to indicate the mapped field.

Then there is a \v switch, which will probably not be used by very many folks attending today's WebCast, but it is designed to allow Japanese addresses or other East Asian addresses to be written vertically with the Kanji numbers. Japanese street addresses typically include Western numerals, just like we're used to, 1, 2, 3, 4, 5, 6, 7, and so on, which is the usual way of writing a horizontal address. So when it's written vertically, you're supposed to use Kanji numbers. Writing the Western numerals in vertically is incorrect and this switch causes Word 2002 to automatically correct this behavior. What the switch does is the following: if the language is Korean, no change is made, and then beyond that it replaces Western digits with the equivalent Kanji digits, then it replaces full-width minuses with half-width minuses, and changes half-width letters, A through Z, upper- and lower-case, to full-width letters.

Then we have a whole bunch of switches for the address block and greeting line fields. These include switches for the country mode, which is to never include the country, always include it, or only include it if it's different from a value for the next switch, which is a \e, which tells which country should be suppressed in that situation.

Other switches here (we have full information on them in Word's help file) would be a \e, which indicates what static text to use as a greeting line when we have a contact that does not have a name. Then we've got information for formatting our merge field placeholders, and these are used in constructing the address or greeting line, and what language rules to use to evaluate a field. Then with this \f switch, which is used in laying out the address block or greeting line appearances, there are a bunch of placeholders that can be used, so that we can change the appearance of the address block or greeting line to fit how we want them. This is not something that we really recommend, because its customized format may be ignored if it contains contact fields that are not present in a particular record.

Now, when a standard field is inserted into a document, for instance, the first name field, Word also internally inserts an index into the Standard Fields table (for example, in this case, First()) and references it for the merge. The reason for this is, if we switch to a different language interface such as French, the field name will still be referred to correctly, but the field name displayed will be shown in French. So rather than seeing the English first name, we would see the French translation for that.

On our last slide here for data connectivity, slide 27, we have a note stating that OLE DB is the default connectivity for data access with Word and Mail Merge. OLE DB is an open specification, which is designed to build on the success of ODBC by providing an open standard for accessing all types of data. To update the current data access code in Word, support for OLE DB data access through the Office datastore object has been added.

OLE DB here is the successor to ODBC. OLE DB is a Microsoft strategic system-level programming interface to data across the organization and all products. ODBC was created to access relational databases, but OLE DB is designed for relational and non-relational information sources. This would include hierarchical databases, e-mail and file system stores, text, graphical and geographic data, custom business objects, and many more types of objects and databases.

OLE DB defines a collection of COM interfaces that encapsulate various database management system services. This enables the creation of software components that implement such services. OLE DB components consist of data providers, which would contain and expose data; data consumers, which use the data; and then service components, which process and transport data. These would be things such as query processors and cursor engines. In addition, OLE DB includes a bridge to ODBC to enable continued support for the broad range of ODBC relational database drivers available today.

You'll see that the next note here is that Word 2002 removes DDE as the standard for accessing Microsoft Excel and Microsoft Access data. You can have or still use DDE for backwards compatibility, so even though it isn't used by default, you can turn on the Confirm conversions at open option in Word's general options to be able to get the choice to set DDE as the method for your data connection. After it's set for the active main Mail Merge document, DDE, data access, will continue to be used for that document. So once it's set for a given main document, it will stay that way.

Then the last thing, as we noted a little bit before, we have made great improvements when using Outlook as the data source. It is a whole lot easier to use Outlook as a Mail Merge data source in Word 2002 because of improvements such as using Outlook field names in the list of standard merge fields, so that the mapping is automatic. We support more Outlook contact fields than before, and we also support the contains operator in our filtering for use with the Categories field.

Also, note that now the integration with Outlook is also via OLE DB. This bypasses Outlook's specific data retrieval that was done before, which was using a converter file. Mainly, this means it's easy for us to refresh the data in our merge. Also, when we reopen a main document that was using Outlook Contacts as the data source, it will automatically connect to the Outlook Contacts, rather than trying to use the converted set of contacts that was created before.

That pretty much concludes the overview of Mail Merge in Word 2002. Now we will go to questions.

Jason Bennett: Great. Thank you for that presentation, Richard. We are ready to move into the Q&A portion of our WebCast, but I have a couple of quick notes before we move into that.

If you joined this broadcast late or would like to review the content again, we will have the on-demand streaming media available within about eight hours of the live session on our Web site on the Past Support WebCasts page. To access information for all upcoming Support WebCasts and the archived content from all past WebCasts, an easy to remember URL is http://support.microsoft.com/webcasts/.

The Q&A portion of the Support WebCast is intended to encourage further discussion of the Support WebCast topic. One-on-one product support issues are outside of the scope of the Support WebCast. If you do need technical assistance, please submit an incident on the Web or call Microsoft Product Support Services and speak to a support professional.

With all of those details out of the way, let's go ahead and jump into the questions. The first question we have is, We frequently merge 20,000 to 60,000 records; however, we can only print or merge about 1,800 records before Word runs out of RAM and the PC locks up. What can we do to increase the ability to merge all of those documents? Add RAM, add dual processors, or add a second hard drive? What would work best to increase the capabilities of Word 2002?

Robert: Usually, in this kind of a situation, RAM is not where our problem occurs. Our problem, typically, in this situation, is going to occur because we ran out of temporary space on the hard drive in our temporary location while we were trying to create all of the merge documents. That's typically the main reason. Also, beyond that, the large amount of spooling, if we're trying to merge directly to printers, is going to create large spool files as well. So hard drive space is usually the main limiter in this situation, although not always. With large numbers of records like that, another thing is that the more complex your merge document is, for instance, if it contains any graphics and that sort of thing, as it's going through the process it ends up taking a whole lot of temporary hard drive space.

Jason: Okay great. The next question we have is, How do you use an Access query as a Mail Merge data source?

Robert: Using the Access query as the data source would normally be a method of opening existing data and browsing to the Access database file and then just telling it that you want to open it. When you open it you get a choice, and it lists the tables and normally the list of queries that are part of your Access data source. That should be all there is to it. If you're having problems beyond this and the queries are not showing up in the list, then it may be best to go ahead and contact us directly first for more support on it.

Jason: Okay. The next question in the queue, Our company uses the term ADDR1 for address 1 in our databases. Is there a way to make Word automatically recognize this every time a database is opened?

Robert: There really isn't. If the smart mapping of data fields in Word 2002 is not picking it up, then there's really not a good way for us to force it to always pick it up. It's generally looking at the field names and just doing its best to try and match them up. This example is one that I would normally expect it to manage to match up, but if it's not, I'm not sure if there's any other way that we could improve that, at least in what we can change in the current version. It's something that could definitely be looked at and improved in future versions, though.

Jason: Okay. The next question, The Office Data Store is new to me. Is this the DB container for OL2002 or is it a part of MDAC?

Robert: It really isn't either one. It's not something that I'm totally clear on because it's more a part of the data access structure. It probably, if anything, fits closest with the MDAC. Again, that's something that, because I'm not clear on it, I can't provide a very good answer for it, although, there's probably more information on it on our Web site in the Data Access section.

Jason: What method of data access would be used to use a public Contacts folder from Exchange 2000?

Robert: Trying to use a public folder. The only way is to go through Outlook, unless some sort of custom provider was created. That is my general opinion here, although that's not something that I have seen or taken a good look at in the past, so I'm not 100 percent on that.

Jason: Okay. Next question, What changes have been made to processing conditional text?

Robert: I'm not 100 percent sure what they mean with the question, but I'm thinking that they're probably talking about the use of IF fields within a merge. Really, there have been little or no changes to that. It still works pretty much exactly as it has in past versions.

Jason: Okay. Next question, How do I use merged fields in the subject of an e-mail?

Robert: Unfortunately, at this time, we don't have any direct way for that to be done. It's just the limitation of the design at this point.

Jason: Okay. Next question, I have two Contacts folders in Outlook, but the Choose Folder dialog in the wizard only shows the default Contacts. Any thoughts?

Robert: The thought there is that, usually, one of them, for whatever reason, is not set up properly in Outlook to show up as an Outlook Address Book. You set that in the properties of the Contacts folder within Outlook. If they're both set as Outlook Address Books, and only one shows up, then the only other thing I could think of to try there would be changing the folder name and see if that makes any difference.

Jason: Okay great. Next question, Does Word 2002 support dual processing?

Robert: Not really anymore than it has in the past. When working within Windows NT® or Windows 2000 on a multiprocessor machine, there are certain things like background printing and background grammar and spell checking that may be able to take advantage of dual processing because another thread is being spun off of the application. But there's nothing specifically that I know of that's been done to Word in 2002 to change it from Word 2000 in this aspect.

Jason: Okay great. Can we also use SQL Server views or tables as a data source?

Robert: Yes. OLE DB makes it as easy for us to use SQL Server tables and views as any other data source, such as an Access database file.

Jason: The next question, We use several folders within Outlook to store contacts. How do we get Mail Merge to use a different folder rather than the default Contacts folder?

Robert: That's pretty much the same question we had a couple questions back. Again, if they're all set up as Outlook Address Books, you should get a choice to choose which one of them you want to use.

Jason: Okay. Next question, What links could you recommend for further reading on Word 2002?

Robert: I would recommend visiting http://office.microsoft.com/assistance/ and http://support.microsoft.com/directory/content.asp?ID=FH;EN-US;wd2002&FR=0&SD=GN&LN=EN-US&CT=SD&SE=NONA/.

You can also search the Microsoft Knowledge Base at http://support.microsoft.com for Microsoft Word 2002 articles on whatever topics you are looking for.

Jason: The next question we have is, Can you use a different e-mail product besides Outlook?

Robert: You really can't, with the exception of Outlook Express. The main limitation is for certain things we have to have a full MAPI implementation. Outside of Outlook, there really aren't any other full MAPI implementations in other products.

For merging to plain text, we could use most other MAPI-compliant mail programs, which is exactly what we do when we use Outlook Express as the workaround to the Outlook security model for plain text e-mail merges. I would think, in that situation, that Eudora, for example, should work, and any others that provide a full, simple MAPI e-mail implementation would probably work in that situation, but they have not been tested.

Jason: Okay. Next question, What is the name of the specific Word object that exposes Merge Mail to VBA?

Robert: It's going to be pretty much the same as it's been in the past, and that's going to be the various Mail Merge objects within the Word object model. There are quite a few different objects and commands, and those can be found fairly easily just by looking at the term MailMerge (as one word) in the Object Browser when you're in the VBA Editor from Word.

Jason: Okay. The last question is, In Word 97 we experienced a problem with Word converting barcodes from ZIP codes and addresses. We were forced to use the field name DPBC. Has this problem been addressed in Word 2002?

Robert: Well, because I'm not really sure exactly what problem they are encountering, it's difficult to answer that question definitively. There's not that much difference in the barcode field in later versions than in Word 97, beyond the fact that it's a whole lot easier to put in and specify which of your fields apply to different parts of the barcode.

Jason: If that user has any more questions, that is probably a product support question and they'd want to contact Microsoft Product Support Services and speak to a support professional.

That does look like we've cleared the queue of all our questions. That is going to wrap up our session. I do want to take a moment to ask for your feedback. If you have any suggestions for topics for future Support WebCasts, you can send those to us using the alias feedback@microsoft.com and include "Support WebCasts" in the subject line. If you have any other comments or questions about today's presentation, please do the same and we'll follow up with you.

We hope you join us again in the near future. Thank you and goodbye.