Top Navigational Bar

WP 5.1's {NEST PRIMARY} Command Different Tha
DocumentID: 654300
Revision Date: 29-Feb-96 8:29:30 PM

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

Problem

Symptoms: In WordPerfect 5.1, if the customer has a primary merge file set up with {NEST PRIMARY}{FIELD}3~~ and field 3 happens to be blank, the merge goes into an endless loop and merges the same record repeatedly. In WP 5.0, if the customer uses ^P^F3^^P and field 3 was blank, the merge still merges all of the records from the secondary file. Solutions: You can easily get around the difference between 5.0 and 5.1 by using the following commands:
{IF NOT BLANK}3~{NEST PRIMARY}{FIELD}3~~{END IF}

When merging, all formatting commands encountered in the primary file get transferred to the new file. If you are attempting to prevent a blank line, the [HRt] code will need to be between the {IF NOT BLANK} and the {END IF} commands.

This should be used carefully, since you are nesting primary files and not chaining them. Refer to the WordPerfect Reference Manual for information about Level, Nesting, and Chaining. WP 5.0's ^P command simply retrieves the specified file and continues the merge at that point. The 5.1 merge process is designed differently.

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.