QlikView Reference Manual.pdf - QlikCommunity - QlikView

DayNames
The format defined replaces the weekday names convention of the operating system (Regional Settings).
Example:
Set DayNames='Mon;Tue;Wed;Thu;Fri;Sat;Sun';
LongDayNames
The format defined replaces the long weekday names convention of the operating system (Regional
Settings).
Example:
Set Long-
DayNames='Monday;Tuesday;Wednesday;Thursday;Friday;Saturday;Sunday';
Back to Other Functions.
Error Variables
The following variables can be used for error handling in the script:
ErrorMode page 278
ScriptError page 278
ScriptErrorDetails page 279
ScriptErrorCount page 279
ScriptErrorList page 279
The values of all five variables will remain after script execution. The value of the last four variables, for
error handling inside the script, is of course dependent on the use of ErrorMode=0.
ErrorMode
This variable determines what action is to be taken by QlikView when an error is encountered during script
execution. By default (ErrorMode=1) the script execution will halt and the user will be prompted for action
(non-batch mode). By setting ErrorMode =0 QlikView will simply ignore the failure and continue script
execution at the next script statement. By setting ErrorMode =2 QlikView will trigger an "Execution of
script failed..." error message immediately on failure, without prompting the user for action beforehand.
Example:
set ErrorMode=0;
ScriptError
Returns the error code of the last executed script statement. This variable will be reset to 0 after each successfully
executed script statement. If an error occurs it will be set to an internal QlikView error code. Error
codes are dual values with a numeric and a text component. The following error codes exist:
1 No error
2 General Error
278