Text |
No data defined in program. |
Explanation |
The program (or subprogram, subroutine, helproutine) to be displayed in the top half of the editing screen does not contain any explicit field definitions. |
Action |
Check program to be displayed, and have the data area used by the program displayed to see the desired variables. |
Text |
Field/parameter type is missing. |
Explanation |
Field/parameter type must be specified. |
Action |
Enter a field/parameter type. |
Text |
Do not enter starting value for an index which is '0'. |
Explanation |
For a dimension whose index is '0' you cannot specify a 'Starting from' value. |
Action |
Either specify an index, or remove starting value. |
Text |
Dynamic layout not possible for WRITE statement. |
Explanation |
You cannot use a dynamic layout map for a map that is to be output via a WRITE statement. |
Action |
Correct error. |
Text |
Verification name already exists, but is not a free rule. |
Explanation |
The verification you have specified already exists and is defined in Predict as an automatic rule. |
Action |
Specify other verification name. |
Text |
Rejected by Predict defaults. |
Explanation |
The switch 'Rule in Map Editor' in the Predict Defaults is set to 'D' (disallowed). |
Action |
Ask your Predict administrator to change the default. |
Text |
Do not enter a rule name and source text at same time. |
Explanation |
Enter either a free rule name to include the rule source from Predict into the rule editor, or enter source text, press ENTER and then enter a rule name to save the source in Predict. |
Action |
Remove either the rule name or the source text and press ENTER again. |
Text |
Do not apply a processing rule to an output field. |
Explanation |
A processing rule that is attached to an output field is not executed. |
Action |
Remove the processing rule or change the field class. |
Text |
An internal error occurred. |
Text |
Memory allocation failed. |
Action |
Save your work and try to free computer resources. |
Text |
Bad object handle detected. |
Explanation |
Natural received an object handle that does not identify an object. A programming error in an application has assigned an illegal value to an object handle. |
Action |
Check and correct program. |
Text |
Bad value in Attribute type. |
Explanation |
An illegal value has been assigned by an application program to the Attribute. |
Action |
Check and correct program. |
Text |
Invalid value assignment for a SUPPRESS-XXX-EVENT Attribute. |
Explanation |
A value has been assigned to one of the SUPPRESS-XXX-EVENT Attributes that is not permitted. |
Action |
Consult the documentation for permitted values and correct program accordingly. |
Text |
Bad parent type. |
Explanation |
The object referred to by the PARENT Attribute is of an incompatible type. For example, a List Box Item requires a List Box Control as a parent. |
Action |
Check object type in the documentation. |
Text |
Bad object handle detected in Attribute SUCCESSOR. |
Explanation |
The Attribute SUCCESSOR does not refer to an object. |
Action |
Check and correct program. |
Text |
Natural cannot perform requested action. |
Explanation |
A Natural application has tried to perform an operation on an object that does not provide for such an operation. |
Action |
Consult your documentation for valid operations and correct your program accordingly. |
Text |
Invalid data type. |
Explanation |
The Natural data type used for the parameter value does not match the type required by Natural. |
Action |
Consult your documentation for type compatibility and correct your program accordingly. |
Text |
Invalid font description. |
Explanation |
The font description in the Attribute STRING is invalid. |
Action |
Check and correct program. |
Text |
Font handle not valid. |
Explanation |
The FONT-HANDLE Attribute does not refer to an object of the type Font Control. |
Action |
Check and correct program. |
Text |
Bad index or position value specified in NGU subprgm parameter. |
Action |
Check and correct program. |
Text |
Bad start position value specified in NGU subprogram parameter. |
Action |
Check and correct program. |
Text |
Bad end position value specified in NGU subprogram parameter. |
Action |
Check and correct program. |
Text |
Bad value in parameter 'text-length'. |
Explanation |
The value in the parameter 'text-length' is smaller than the difference between the values of the parameters 'start-position' and 'end-position'. |
Action |
Check and correct program. |
Text |
Bad value in parameter 'line-from'. |
Action |
Check and correct program. |
Text |
Bad value in parameter 'line-to'. |
Action |
Check and correct program. |
Text |
Bad value in parameter 'column-from'. |
Action |
Check and correct program. |
Text |
Bad value in parameter 'column-to'. |
Action |
Check and correct program. |
Text |
Bad value in parameter 'colour-name'. |
Explanation |
This can occur for the Attributes FOREGROUND-COLOUR-NAME or BACKGROUND-COLOUR-NAME. |
Action |
Consult your documentation for permitted values and correct program accordingly. |
Text |
Attribute cannot be modified. |
Text |
Natural could not create window. |
Action |
Check your program and ensure that you have sufficient system resources. |
Text |
Natural could not create Dialog Element. |
Action |
Check your program and ensure that you have sufficient system resources. |
Text |
Attempt to create Menu Item failed. |
Explanation |
There is an internal limit for the number of Menu Items per menu. Try to limit the number of your menu items to a manageable number. Human engineering studies recommend a maximum of 7. |
Action |
Check and correct program. |
Text |
Keyword OBJECT in the handle definition expected. |
Explanation |
On non-GUI platforms only object handles (HANDLE OF OBJECT) may be defined. |
Action |
Check and correct handle definition. |
Text |
Operand2 must be defined as a handle variable. |
Action |
Check and correct program. |
Text |
Operand format is not INTEGER or length is invalid. |
Explanation |
An operand of format INTEGER is required for this operand. - The dialog id of the OPEN DIALOG, SEND EVENT or CLOSE DIALOG statement does not have format/length (I4). - The GIVING operand of a CREATE OBJECT or SEND METHOD statement does not have format/length I2 or I4. |
Action |
Correct format/length definition of the operand. |
Text |
Parameter-name not defined. |
Explanation |
Parameter-name not defined in DEFINE DATA PARAMETER section. |
Action |
Check and correct program. |
Text |
Statement/variable/constant not permitted on non-GUI platforms. |
Explanation |
The program contains elements, such as the OPEN DIALOG statement, that are only applicable to GUI platforms. |
Action |
Check and correct program. |
Text |
Invalid Attribute value. |
Explanation |
The value that has been assigned to the Attribute is illegal in this context. |
Action |
Assign a valid Attribute value. |
Text |
Incompatible Attribute name specified. |
Explanation |
Attribute name is not in the set of allowed Attributes for the Dialog Element type. |
Action |
Choose an allowed Attribute for this Dialog Element type. |
Text |
Invalid Dialog Element type specified. |
Explanation |
This Dialog Element type is not available. |
Action |
Consult your documentation and enter a valid Dialog Element type. |
Text |
Invalid Attribute name specified. |
Action |
Consult your documentation and choose an allowed Attribute name. |
Text |
Attribute must not be queried. |
Explanation |
For this Dialog Element type, you must not query the value of this Attribute. |
Action |
Correct program. |
Text |
Attribute must not be modified. |
Explanation |
For this Dialog Element type, you must not modify the value of this Attribute. |
Action |
Correct program. |
Text |
Event queue overflow. |
Explanation |
During a long user interface operation, too many events have occurred. For example, the user has scrolled in a scrollbar by holding down the mouse button for a long time, which has caused too many timer events to occur in the meantime. |
Action |
When interacting with the user interface, interrupt from time to time. |
Text |
Format error in dialog definition. |
Explanation |
The dialog editor has detected a format error
in the dialog definition.
Possible causes:
1) Source data has been corrupted in the storage
medium.
2) Source has been generated incorrectly because
the source has been edited with another
editor or utility.
3) The dialog object has been created and stored
with a version of the dialog editor that is
incompatible with the current version of the
dialog editor. |
Action |
1) Upgrade your Natural development environment. 2) If a dialog box appears offering you the choice to continue, you may be able to work with the dialog |
Text |
Format error in dialog source at line :1:. |
Explanation |
The dialog editor has detected a format error
in the dialog source at the line indicated.
Possible causes:
1) Source data has been corrupted in the storage
medium.
2) Source has been generated incorrectly because
the source has been edited with another
editor or utility.
3) The dialog object has been created and stored
with a version of the dialog editor that is
incompatible with the current version of the
dialog editor. |
Action |
1) Upgrade your Natural development environment. 2) If a dialog box appears offering you the choice to continue, you may be able to work with the dialog. |
Text |
XREF request disallowed by Natural Security definition. |
Explanation |
In a Natural Security environment, XREF can only request settings that provide more detailed information than defined by means of the Natural Security profile that applies. The following table shows the possible combinations (valid combinations marked with "+"): Definition I Request by XREF command in Natural I Security I profile I OFF ON FORCE -------------+----------------------------- OFF I + + + ON I - + + FORCE I - - + |
Action |
Check data and correct error, or contact the DBA to modify the appropriate security profile. |
Text |
Function not possible with DBID = 0. |
Explanation |
To generate the Natural cross references the DBID of the Natural system file, where the module is to be stored, must not be zero. |
Action |
Contact the DBA to generate a valid Natural parameter module or invoke Natural and overwrite the value of the data base identification dynamically. |
Text |
Invalid input data. |
Explanation |
Invalid data have been specified for the field. |
Action |
Specify valid input data. |