Report Writer error messages

A list of configuration error messages. For messages that are not self-explanatory, additional information is provided.

Table 1. Report Writer error messages
Number	Description
GS-18001	`file not found`
GS-18002	`Data schema is missing, specify -data <path> argument`
GS-18003	`Need one and only one root in data schema`
GS-18200	`This version of fglrun is not supported` The `fglrun` tool is a runtime system program. For further information, see the fglrun topic in the Genero Business Development Language User Guide.
GS-18205	`calls in wrong order; need to call fgl_report_load first` Settings must be loaded before they can be committed. For further information, see Usage: load and commit.
GS-18234	`cannot write to file fgl_getenv("GREDATAFILE")` The GREDATAFILE environment variable is used to generate debug information. For further information, see Report an issue to support.
GS-18265	`environment variable GREDIR is not set` The GREDIR environment variable specifies the installation directory of the Genero Report Engine (GRE). For information about configuring environment variables, see Environment sets.
GS-18266	`Unknown driver driverName: Can't find driver in information database`
GS-18267	`Driver driverName is erronuosly supplied with format inputFormat. The driver requires format requiredInputFormat.`
GS-18268	`Device type device is only available when a .4rp design file is specified (not available for auto format reports)` For information about auto format reports, see Running a Genero ASCII report using GRW (compatibility report).
GS-18269	`Failed to open file` This error is issued from the fgl_report_commitCurrentSettings function. The file specified in the call to fgl_report_loadCurrentSetting() could not be opened.