Error messages regarding logic syntax can be reported in these instances:
When using a text editor to create or edit a job specifications file (*.job), you should always use the Run syntax check only option in Run|Tables to check for logic and/or syntax errors before you run tables.
When you use the WinCross Interface to create job specifications, syntax is automatically checked as you enter row, table or filter logic, or when you create glossary variables. However, WinCross may still detect errors when tables are run.
If an error is encountered while running tables, processing stops while the error is written to the report log file (*.lg). The report log file is then automatically displayed. Error messages in the report log are preceded by ERROR: highlighted in red. Warning messages in the report log are preceded by WARNING: highlighted in blue. Search tools are provided at the top of the report log to help with locating specific errors, warnings or text.
In the example above, double-clicking the ERROR messages, will open the job file and position the cursor on the appropriate line in the job file where the error occurs. In the example above, double-clicking the WARNING message, would have no effect because there is no line number associated with that warning message.
Search tools are provided at the top of the Report Log dialog for help in locating specific warnings, errors or text values:
You can manually view the log file any time using View|Report Log and/or print it using File|Print|Print Report Log (since the log file is in ASCII format, you can also print it from text editors such as Wordpad or Notepad). When printing the job file (*.job) using File|Print|Print Job, WinCross inserts line numbers for reference so you can easily find an error location within the job file. View|Job File will also reference the line number for a specific line when you click on a line in the job file. The line and column number are displayed at the bottom of the job file dialog box. Once you have corrected the error(s), run the tables again. Repeat this process until no more errors are reported.
Most error messages refer to logic syntax errors. Refer to Logic Structure for details regarding logic, logic instructions and glossary variable commands. You might also want to refer to Writing Specifications Using a Text Editor for additional information.
Related topics: