Table of Contents
Advertisement
ERROR
MESSAGES
ERROR
MESSAGES
MEANING
•
CAUSE
NEXT
without
FOR
A
variable
in
a
NEXT
statement does not correspond
to
any
previously
executed,
unmatched
FOR
statement
variable.
Syntax
error
A
line
is
encountered
that
contains
some
incorrect
sequence
of characters (such
as
an
unmatched
parenthesis,
misspelled
command
or
statement,
incorrect
punctuation,
etc.)
RETURN
without
GOSUB
A
RETURN
statement
is
encountered
for
which
there
is
no
previous,
unmatched
GOSUB
statement.
Out
of
DATA
A
READ
statement
is
executed
when
there
are
no
DATA
statements with unread data remaining
in
the
program.
Illegal
function
call
A
parameter
that
is
out
of range
is
passed
to
a
math
or
string
function.
An
"Illegal
function
call"
error
may
also
occur
as
the
result.
Overflow
The
result
of a calculation
is
too
large
to
be represented
in
BASIC number
format.
If
underflow
occurs, the
result
is
zero
and
execution continues without an
error.
Out
of
memory
A
program
is
too
large,
or has
too
many
FOR
loops,
GOSUBs,
or
too
many
variables.
Underfined
line
number
A
nonexistent
line
is
referenced
in
a
GOTO, GOSUB,
IF
...
THEN
...
ELSE,
or
DELETE
statement.
A
new
program
line
that
contains only the
line
number,
also
causes
this error.
Subscript out
of
range
An
array
element
is
referenced
either
with
a
subscript that
is
outside the
dimensions
of
the array
or with the
wrong number
of subscripts.
Redimensioned
array
Two
DIM
statements
are
given
for
the
same
array;
or, a
DIM
statement
is
given
for
an
array after
the default
dimension
of
10
has
been
established of that
array.
Division
by
zero
A
division
by
zero
is
encountered
in
an
expression; or the operation
of
involution
results
in
zero
being
raised
to
a
negative
power.
Illegal
direct
A
statement
that
is
illegal in
direct
mode
is
entered
as a direct
mode command.
Type mismatch
A
string
variable
name
is
assigned
a
numeric
value or
vice versa; a
function
that
expects
a
numeric
argument
is
given
a
string
argument
or vice
versa.
Out
of
string
space
String variables
have caused
BASIC
to
exceed
the
amount
of
free
memory
remaining
which
has
been
allocated for
string
operations
by
CLEAR
statement.
String
too
long
An
attempt
is
made
to create
a string
more
than
255
character
long.
String
formula too
complex
A
string
expression
is
too
long or
too complex.
The
expression should be
broken
into
smaller ex-
pressions.
Can't
continue
An
attempt
is
made
to
continue
a
program
that;
1.
Has
halted
due
to
an
error.
2.
Has been modified
during
a
break
in
execution.
3.
Does
not
exist.
Underfined
user
function
A USR
function
is
called
before the function
definition
(DEF
statement)
is
given.
Device I/O
error
An
error
occured on an
I/O device operation.
Verify error
The
contents
of
memory
and
the contents of
a
file
turn
out
to
be
different.
This
error
may
occur
when
using
CLOAD?
command.
No
RESUME
An
error
handling routine
is
entered but contains
no
RESUME
statement.
RESUME
without
error
A RESUME
statement
is
encountered
before an
error
handling routine
is
entered.
Unprintable
error
An
error
message
is
not
available for the
condition
that
exists.
Missing
operand
An
expression contains an operator with
no operand
following
it;
a
command/statement
is
given
without
its
compulsory
parameters.
Line buffer
overflow
An
attempt
is
made
to
INPUT
a
line
that
contains
more
than
255
characters.
Field
overflow
A
FIELD
statement
is
attempting
to allocate
more
bytes than
were
specified for the
record
length
of
a
random
file.
Internal error
An
internal
malfunction
has
occurred
in
MSX
BASIC. Report
to
Microsoft the conditions
under
which
the
message
appeared.
Bad
file
number
A
statement
or
command
references
a
file
with
a
file
number
that
is
not
OPEN
or
is
out
of
the
range
of
file
numbers
specified
at initialization.
File
not
found
A
LOAD,
KILL,
NAME,
or
OPEN
statement/command
references
a
file
that
does
not
exist
on
the current
disk.
File
already
open
A
sequential
output
mode
OPEN
statement
is
issued for a
file
that
is
already
OPEN;
or
a
KILL
statement
is
given
for
a
file
that
is
OPEN.
Input
past
end
An INPUT
statement
is
executed
after
all
the data
in
the
file
has
been
INPUT,
or for
a
null
(empty)
file.
To
avoid
this
error,
use the
EOF
function
to detect
the
end
of
file.
Bad
file
name
An
illegal
form
is
used
for
the filename with
a
LOAD, SAVE,
KILL,
or
OPEN
statement
(e.g.,
a
filename with too
many
characters).
Direct
statement
in
file
A
direct
statement
is
encountered
while
LOADing
an
ASCII
file.
The
LOAD
is
terminated.
Sequential I/O
only
A
GET,
or
PUT
statement
is
used with
a
file
that has
been
OPENed
as a
sequential
file.
File
not
OPEN
An
I/O
command/statement
is
used with
a
file
that has
not been
OPENed.
Advertisement
Table of Contents
