Warning messages indicate possible problem areas in a QA Build program. In some cases, an effect may be intentional, and the message can be disregarded. In other cases, the message will highlight an oversight on the part of the developer.
Warning 1. You have already processed this field
|
Cause |
A key field is processed twice before the record is defined |
|
Action |
None |
Warning 2. Accessing non key fields before key explicitly set up. Assuming required key set up before this field
|
Cause |
Non key fields are processed before the key of the record is set up |
|
Action |
If the table is to be accessed by a secondary index, make sure this is stated in the table processing |
|
Cause |
The table is being auto incremented, and the incremented key is not displayed |
|
Action |
No action is necessary, but the message will clear if the field is set up as a no display field in the field processing |
|
Cause |
The same map is used in different procedures which process the table using different indexes |
|
Action |
Add duplicate fields so that the fields can be processed in the correct order in both procedures |
Warning 3. Input field found in non interactive procedure – switched off
|
Cause |
Field processing exists for input fields (this may be because an interactive procedure has been modified for use as a non interactive procedure) |
|
Action |
No action is necessary. To suppress the message, change the Input flag in the field processing |
Warning 4. Changing key field after record accessed
|
Cause |
One of the fields used to access the record is input to or assigned a new value after the record is already accessed |
|
Action |
If this is intentional, no action is required |
|
Cause |
A non key field is processed before a key field |
|
Action |
Change the order of field processing |
Warning 5. Too little memory for multiple choice access on table <table name> in procedure body <body name>. Exact match search used instead
|
Cause |
The program is very large |
|
Action |
Reduce the size of the program. See the suggested action for Fatal Errors 1, 2 and 3 |
Warning 6. Table <table name> is totalled into without being updated
|
Cause |
A database field is specified for totalling into, but the table processing does not specify that the table is to be updated |
|
Action |
Modify the table processing if necessary |
Warning 7. Including update procedure in report/enquiry program. Updates switched off
|
Cause |
A procedure has been set up to update the database in a Report or Enquiry program – perhaps the procedure has been copied from a Data Entry program |
|
Action |
To clear the message, modify the procedure body description and the table processing |
Warning 8. Deleting without asking first in interactive procedure
|
Cause |
You have not set up a map for the Record deletion dialog question in table processing |
|
Action |
If you do not set one up the record will be automatically deleted, without user confirmation |
Warning 9. %option <command> should be < > in program command
|
Cause |
You have misspelled a %option command. For example, %bath instead of %batch |
|
Action |
Correct the spelling |