HP Data Entry and Forms Management System (VPLUS) Reference Manual (32209-90024)

310 Chapter6
USING VPLUS INTRINSICS
INTRINSIC DESCRIPTIONS
to fit into a VFORM file. Now, VMERGE gives you an alternate method for generating VFAST
files that contain additional forms. However, VFAST files still have limited capacity, and so
there are still limits on the total number of forms you can place in a forms file, even using
VMERGE.
Initial analysis shows that the ratio of fast form file size to slow form file size is around 1/3
to 1/10. This suggests that you can expect to combine forms from three or more nearly full
(to FORMSPEC) forms files into one forms file, by using VMERGE. However, this is an estimate
only, since non-typical forms files may vary considerably in their object to source ratios.
Input File Compatibility
Not all forms files can be successfully combined using VMERGE. The input forms files must
be “compatible” in order to be combined with VMERGE. The compatibility factors are:
• Form names -- the same form name may not appear in both the VMASTER and the VAUX
files.
• Save fields -- if both input files use save fields, the specifications for both files must be
identical in all respects: names of save fields, lengths, data types, and initial values. The
save fields must also be defined in the same order. It is permissible for one file to use
save fields and the other not to do so.
• Global function key labels -- if both input files define global function key labels, the
specifications for both files must be identical in all respects. It is permissible for one file
to define global function key labels and the other not to do so. In this case, the global
function key labels from the file which contains them will be retained in the output file.
• Terminal selection and language id -- both input files must have exactly the same set of
terminals selected and the same Forms File Language specified (from FORMSPEC
Terminal/Language Selection Menu).
There are a number of forms file characteristics that may differ between the two input files
that are not serious enough for VMERGE to consider the two files as incompatible. These
include: head form name, error enhancement, window display line, error window color, and
window enhancement. The characteristic found in the VMASTER file is retained in the
VOUTPUT file.
Application Requirement for Combined Forms Files
VMERGE takes two FORMSPEC-compiled forms files specified by the VMASTER and VAUX file
designators, extracts the object forms from each file, and places these forms in a VFAST file
specified by the VOUTPUT file designator.
Every forms file has a $HEAD form designated for it. Additionally, every form in a forms file
has a “Next Form” designated for it. Next Form may be $HEAD or it may be the name of
another form in the file. In order to compile a forms file, FORMSPEC requires that any form
named as the $HEAD or as a Next Form exist in the file. Consequently, it is impossible for a
form in the VMASTER forms file to refer to a form in the VAUX forms file as its Next Form and
vice versa.
Therefore, the application program used with a combined forms file must be coded to
sequence among the forms in the combined forms file without depending on the Next Form
designation. The Next Form designation can only be used when it and the current form