Download DataCheck

Log Item Definitions
Error
Number
Description
Detail
Action
97
File system error
accessing EOF (file:
’<1>’)
DataCheck determines the size
of a file by jumping to the end of
the file and then asking the operating system what file position it
is at. If there was a problem in
either of these operations, then
DataCheck reports this error. It is
most likely a file system problem.
Use a file system tool such as
Norton Utilities to uncover the
problem.
98
Claimed file size
greater than actual file
size (file: ’<1>’, claim:
<2>)
The size of the data file is stored
within the data segment information table. If this claimed size is
greater than the actual file size,
then DataCheck complains. This
is indicative of a file truncation.
You should probably go to a
back up of this file. You might
be able to recover your data
using a disk utility, but your
backup is really your best bet.
99
Cannot read Table
Information Table
Header
The table information table
header contains information
such as the number of tables in
the database, what the offset to
the index header tables are, how
many indices there are, and the
like. If this cannot be read, then
there is most likely some severe
damage in your data file.
Recover by TAGS is probably
your only bet.
100
Too many tables (max:
<2>, claim: <1>)
Only 255 tables can be used by
4D. If the number of tables
stored in the table information
table header is greater than this,
then DataCheck complains.
Most likely, this is indicative of
damage.
You should recover by TAGs.
101
Cannot read Table
Information Table
The Table Information Table
stores information about each
table, such as how many records
there are, where the address
tables are stored on disk, and
the like. All table information
tables are read in one shot by
DataCheck. If it can’t read all of
them, then it bails, assuming that
there is severe damage. This
item is then generated.
Recover by TAGs.
102
Too many records
(table: <1>, claim: <2>)
A table can only have 16777215
records. If the number of records
is greater than this, then there is
some damage in your table information table for the given table.
You should recover by TAGs.
69