HP Data Entry and Forms Management System (VPLUS) Reference Manual (32209-90024)
Chapter 3 89
INTRODUCTION TO FORMS DESIGN
FORM FAMILIES
The solution to this problem of long user waiting time is to create two forms with the same
form layout but different field attributes.
Suppose the root or parent form of this example is named CUSTPAR, and that its form
layout is as shown in Figure 3-15. below. All of the fields in this form are display only,
except for the Customer ID Number field, which is required.
Figure 3-15. Parent Form
Create a child form, CUSTCHILD, by specifying CUSTPAR in the "Reproduced from" field of
the Form Menu. Press
NEXT until the Field Menu for CUSTID appears and make it a
display only field. Make all other data fields in the form optional. Compile the forms file.
Figure 3-16. Child Form
Now when the user types the customer ID and presses
ENTER, the application retrieves
the related information from the database and displays it in the form immediately. Once
the form is on the screen, it appears to remain there as long as the user uses the
application, rather than being repainted each time for every customer about whom the
user calls up data.
Customer Record
Customer ID Number Form ID
Transaction Product
Date Number Price Quantity Total
CUSTPAR
Required
Field
Init set to
“CUSTPAR”
Display only
Fields
Customer Record
Customer ID Number Form ID
Transaction Product
Date Number Price Quantity Total
CUSTCHI
Display only
Init set to
“CUSTCHILD”
Optional
Fields