Top Navigational Bar

Merge - Next Record Skipped If Some Fields Bl
DocumentID: 638386
Revision Date: 29-Feb-96 3:04:56 PM

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

Problem

Symptoms: The next record was skipped when a customer used the following syntax to merge a dBASE file in which the last field and second to last fields were blank on some records:
{IF NOT BLANK}17~{FIELD}17~{END IF}{IF NOT BLANK}18~,{FIELD}18~{END IF}
There were two IF statements for each field in the primary file.

Another customer found that the conversion from an ASCII Merge file does not process the delimiters correctly when Field 1 is blank and is referred to as the last field in the primary file.

A third customer found that an ASCII file where the first field was blank did not merge correctly. To solve this problem the customer retrieved the ASCII file as an ASCII Delimited Text (DOS) file and saved it as a WP file. Solutions: When the user used the following syntax, the records were not skipped:
{IF NOT BLANK}17~{FIELD}17~{IF NOT BLANK}18~,{FIELD}18~{END IF}{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 hard return [HRt] code will need to be between the {IF NOT BLANK} and the {END IF} commands.

Status:      Sent to Development
***|sent to dev|***
Press Enter on link token.

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.