Specifications

Resource Compiler Messages Page 12 of 24
#line expected a string containing the file name, found ’token’
A #line directive was missing a required filename.
Resource Compiler Error RC2131
expecting quoted string for key
The field for this statement must be a character string enclosed in double quotation marks.
Resource Compiler Error RC2132
expected VALUE, BLOCK, or, END keyword
A block in a VERSION resource doesn’t end properly, or a new block doesn’t begin properly. This
results in a VERSION statement that is not a valid block.
Resource Compiler Error RC2133
unexpected value in value data
The raw-data values in the RCDATA statement must be integers or strings, each separated by a
comma. Make sure you did not leave out a comma or leave out a quotation mark around a string.
Resource Compiler Error RC2134
BEGIN expected in RCDATA
The BEGIN keyword must immediately follow the RCDATA keyword.
Resource Compiler Error RC2135
file not found: filename
The file specified in the RC command line was not found. Check to see whether the file has been
moved to another directory and whether the filename or path is typed correctly. Files are searched for
using the INCLUDE environment variable or the visual development environment INCLUDE
directory setting (Tools menu, Options item, Directories tab).
Resource Compiler Error RC2136
missing ’=’ in EXSTYLE=<flags>
An equal sign (=) was missing from an EXSTYLE (Extended Style Flags) statement. When the
EXSTYLE is embedded in the DIALOG or MENU statement it must have the following form:
EXSTYLE=FLAGS
Resource Compiler Error RC2137
empty character constant
A pair of single quotes was found with no character specified between them.
Resource Compiler Error RC2138
unmatched close comment ’/*’
An open comment sequence (/*) was not matched with a close comment sequence (*/) This error can
be caused by nesting comments.
Resource Compiler Error RC2139
VERSION not a number
A VERSION resource must be a number.
Resource Compiler Error RC2140
CHARACTERISTICS not a number