Merge Troubleshooting Guide

DocumentID: 10366
Revision Date: 06-Mar-97 3:30:57 PM

The information in this document applies to:
WordPerfect® 5.1 for DOS

Problem

This guide will help you with WordPerfect 5.1 for DOS merge questions. These troubleshooting solutions are similar to the steps a technician will take with you if you call Customer Support. If you find that you are still experiencing problems, please call Customer Support. Creating Test Files The first step is to create test primary and secondary files. Using these test files individually will help you to determine where the problem is occurring. The test primary file can be as simple as a list of necessary fields, each on a separate line of text. Additionally, by merging the test primary file with the test secondary file, it is often possible to verify whether the Merge feature is working correctly. Create a test primary file and merge it with your regular secondary file. If the primary and secondary files do not merge correctly, one of the records in your secondary file is probably causing the problem. Go through the records (starting at the point that you noticed the error) and see what the difference is between those records and the records that seem to merge without a problem. If creating a test primary file didn't solve the problem, create a test secondary file and merge it with your regular primary file. If all of the records merge incorrectly, then the problem is probably in the primary file. Check to make sure that all of the fields are labeled correctly and that the right merge codes have been used. If you are using a code that must be paired with another code, make sure both codes are there; for example, the {IF} statement should have an {END IF} statement. If the fields are merging together correctly but you still have a problem, try one of the following solutions. How Does the Secondary File Look? Does the secondary file look incorrect before you even start the merge? Is so, how was the secondary file created? Did you create it in WordPerfect 5.1, or did it come from another program? If the secondary file is a delimited DOS text file, then it must be retrieved using Text In/Out(Ctrl+F5). Extra Blank Lines Are blank lines appearing where you don't want them? Look for [HRt] codes in the primary file or empty fields in the secondary file. Question Mark Option Did you use the question mark option, such as Field(1?)? Are any attributes such as bold, underline, or large on this same line? If so, this attribute causes WordPerfect to think that line is not blank. As a solution, you could replace the ? option with the {IF BLANK} statement. Duplicate Records Are duplicate records appearing after the merge is complete? Check the secondary file to make sure it doesn't contain any duplicate records. Do any codes follow the last {END RECORD} code? If so, delete the extra codes; they cause WordPerfect to think another record exists.

Answer:

Details:

Product specifications, packaging, technical support and information (*Specifications*) refer to theUnited States retail English version only. Specifications for other versions may vary. All Specifications, claims, features, representations, and/or comparisons provided are correct to the best of our knowledge of the date of publication, but are subject to change without notice.OUR MAXIMUM AGGREGATE LIABILITY TO YOU AND THAT OF OUR DEALERS AND SUPPLIERS IS LIMITED. IT SHALL NOTEXCEED THE AMOUNT YOU PAID TO ACCESS THE INFORMATION. SEE LEGAL DISCLAIMER.