![]() |
"Record Too Large To Sort" |
The information in this document applies to:
WordPerfect® 5.1 for DOS
Problem
PROBLEM: The size of a record that can be sorted has a maximum limit. The record can be no larger than 9216 bytes or approximately five to six pages of regular typed text (based on 1500 bytes per page). The error message associated with this limit is "Record Too Large To Sort." The following are troubleshooting steps for this error message: 1. Reduce the size of the record (see Appendix E, "Record Too Large" in the WP 5.1 Reference Manual). A record in the Sort feature refers to a block of information between the record delimiters. The record delimiter for a paragraph sort is two hard returns [HRt]. The record delimiter for a merge sort is an [END RECORD] code. 2. Check the available disk space and make sure there is 2.5 times the amount of the file size available on the disk. 3. Find where the record transfer stops, look in Reveal Codes for the code [SUBST SECONDARY], delete this code, put in the proper code, save the document, and sort the file. 4. Save the file as ASCII text (Ctrl-F5, 1, 1), retrieve the ASCII file, and attempt the sort again. 5. Verify the sort is defined correctly. One user erroneously sorted a file as a secondary merge sort instead of a line sort. [END RECORD] codes and the message "Record Too Large To Sort" appeared when the customer sorted the file. The user deleted the [END RECORD] codes, changed the sort type to Line, and sorted again. 6. Go to a clear screen and press Ctrl-F9 and select Sort. Then enter the desired filename as the input file and then enter a different filename for the output file rather than having WordPerfect replace the same document. 7. Switch to the Document 2 screen, retrieve the file, and attempt to sort. 8. Attempt to delete the table definition code (after saving the original file first) if the customer is doing a table sort. The customer may be able to sort the information successfully in tabular columns, and then convert the tabular columns to a table. 9. If the customer is doing a table sort, verify all rows are not defined as header rows and that the cursor is inside the table before beginning the sort. 10. If this error appears during a table sort check to see if any of the cells contain more information than can fit in one cell/row. Since a row cannot span a page, WordPerfect will hide information that exceeds the page (the text won't show in Reveal Codes) but the information still exists. One customer received this error when sorting a document in which the parallel columns had been converted into a table. There were two problem rows in the table. One row contained the equivalent of twelve pages of typed text and the other contained nine pages of typed text, both of which exceeded the 9,216 byte limitation for a record. Once the customer removed these rows from the table the sort worked fine. 11. In a secondary merge sort, make sure the [END FIELD] codes are followed by a [HRt] and then the [END RECORD] codes. "Record Too Large To Sort" may appear if the [END RECORD] codes immediately follow the [END FIELD] codes. 12. If the customer is using paired styles in the document, make sure the Style On and Off codes break the document into records that are small enough to sort. One customer got the error "Record Too Large To Sort" because there was a Style On code at the beginning of the twelve page document and a Style Off code at the end with no other style codes in the document. This customer worked around this problem by blocking the text and sorting it. 13. If all the above possibilities have been attempted and each record seems to be set up correctly, try looking through the document in Reveal Codes for any control characters (e.g., ^D) or [UNKNOWN] codes. If these types of codes are found, attempt to delete them and re-sort the file. |
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. |