...
...
In the example below, the value of Error$ is generated by an INCASE() function interpreting the output of a program named ProgX.
The rogX output results are stored in the Telitab set
...
If the result of ProgX_calculation#.ProgX_Errors$ is different from "No errors...", a message box is shown with the error string and with the caption "Error running ProgX". Depending on the type of buttons specified in the dialog by means of the Mode parameter, the session can be either immediately be terminated, or you can decide to let Quaestor attempt to continue the session.
The syntax is as follows.
ProgX_Errors$ = ERROR$(ProgX_calculation#.ProgX_Errors$,INCASE(ProgX_calculation#.ProgX_Errors$ = "No errors...", THEN, "NullString", ELSE, ProgX_calculation#.ProgX_Errors$), "Error running ProgX", 4) + Qcrlf
...
DESP_error_flag$ = ERROR$(INCASE(GET$("Desp.err","NullString", Total_Desp$)="NullString", THEN,
"No errors occurred...", ELSE,
DESP_Errors$)
,INCASE(GET$("Desp.err","NullString", Total_Desp$)="NullString", THEN,
"NullString", ELSE,
GET$("Desp.err","NullString", Total_Desp$)+Qcrlf+Qcrlf+
"Please check your input. Do you want to continue?")
,"In the DESP calculation a fatal error has occurred (details shown below).",4)
If there is any error, it will show a window with the error as available in the file Desp.err including a description of the next step by adding +Qcrlf+Qcrlf+"Please check your input. Do you want to continue?" to the content of the file. In combination with Mode = 4 for the buttons, this makes an understandable error message.
Quick links: Function overview | Attribute overview | Constants overview | Dimensions overview