![]() |
Sort - Secondary Merge Files Not Sorting Corr |
The information in this document applies to:
WordPerfect® 5.1 for DOS
Problem
Solutions: The following information regards problems encountered when sorting secondary merge files: When sorting large merge files, if not all of the records are appearing after the sort is complete, check the merge codes in the document. If the merge ^R codes are entered by pressing Ctrl-R or Shift-6, R the records may not be recognized. The user may need to change all ^R codes to the proper merge R in order for the sort to run correctly. Checking how the merge R and merge E codes have been entered is also helpful when records are not merging correctly. Another possible cause for merge files not to sort correctly is the absence of a hard return between the ^R and ^E or the {END FIELD} and {END RECORD} commands. Another customer sorting a secondary file had trouble with several records not sorting. After looking through the file the user discovered an extra space between the {END FIELD} and hard return [HRt] code of each record that was not sorting correctly. Replacing each space followed by an [HRt] with just an [HRt] code corrected the problem. Merge records will also not sort correctly if a hard page [HPg] or space exists after the {END RECORD} (^E). Another customer was sorting zip codes which were in the last field. The last field ended with an {END RECORD} code, instead of {END FIELD}{END RECORD} code. After the customer added the {END FIELD} code, the user then put the {END RECORD} code on the next line. The sort worked properly after making these changes. Comments at the top of a secondary merge file were sorted into the middle of records. This problem only happens when the user sorts on the first field. The secondary file is set up as follows: Comment: This is my comment {FIELD NAMES}name~address~phone~~{END RECORD} The reason this happened is because the field names code was no longer the first code in the document. To work around the problem, the user can put the comment right after the {FIELD NAMES} code. For example: {FIELD NAMES}[Comment]name~address~phone~~{END RECORD}. If the file is set up in this manner, it will sort and merge correctly. Another customer having problems sorting a secondary merge file found that the hard returns [HRt] placed after the {END FIELD} codes had been deleted. This put all of the fields on one line. WP could not sort the records into the correct order with this format. FYI: One customer wanted to sort a file with a first name {END FIELD} then the last name {END FIELD} on the same line. The program would not sort properly unless there was a space between the first {END FIELD} code and the next name on that line. |
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. |