Answers [ HP ALLBASE/4GL Developer Self-Paced Training Guide ] MPE/iX 5.0 Documentation
HP ALLBASE/4GL Developer Self-Paced Training Guide
Answers
Answer 1. A file (with a record layout and field specifications) must
exist for you to build a module to maintain or inquire on the file.
Answer 2. Both the T edit code and the D edit codes are date formats.
However, fields with the T edit code default to the current date. There
is no default for the D edit code.
Answer 3. When you specify N in the Include all Fields field on the
module builder screen, you must complete the module details screen to
specify which fields the module should include. You must also use the
module details screen if you wish to link fields to a secondary file or
if you wish to alter the on screen label of a field.
Answer 4. No, each secondary file can only be linked to one screen
field.
Answer 5. If you validate a field against a secondary file, any value
that the user enters in the field must match the field in a record in the
secondary file. If no record in the secondary field contains that field
value, an error message is displayed. You cannot move off the field
until a valid entry is supplied.
Answer 6. The name that you give the module is used to name all of the
items that the module builder creates. A complete list of the items, and
their names, is contained in the HP ALLBASE/4GL Developer Reference
Manual.
Answer 7. Yes, the items that the module builder creates are no
different to the items you create.
Answer 8. HP ALLBASE/4GL builds the module in three main steps:
1. Create the resultant screen and the process that calls it.
2. Create all the other application items required.
3. Generate all the module application items.
MPE/iX 5.0 Documentation