User`s guide

1-65
1 to 199
 A corrupt file may be indicated if the file allows variable-length
records and you receive this status code on a Get or Step
operation. In such a corrupt file, you can receive Status Code 54
when you use Get or Step operations to read other records.
Recover the file according to the instructions in Pervasive PSQL
User's Guide.
23: The position block parameter is not 128 bytes long
This status code is obsolete in Btrieve language interface versions 6.0
and later.
The position block parameter must be exactly 128 bytes long.
24: The page size or data buffer size is invalid
The MicroKernel returns this status code in one of the following
situations:
 The page size you specified when creating a file is invalid. The
page size must be a multiple of 512 bytes and cannot exceed 4096
bytes (up to 8.x file format) or 8192 bytes (9.0 file format) or
16384 (9.5 file format).
 During a Create operation, the page size is the first file
specification the MicroKernel checks. If you receive this status
code at this point, it can indicate an invalid data buffer
parameter.
25: The application cannot create the specified file
The MicroKernel returns this status code in one of the following
situations:
 If an application attempted to create a data file, the disk directory
or the disk itself may be full.
 If an application tried to create a file over an existing file, the
existing file is open or the operating system will not allow the
operation for another reason.
 In an attempt to create a Btrieve file over existing Btrieve file, this
status will be returned. The keybuffer on the Btrieve create
operation API (opcode 14) is set properly to create a file over an
existing file.
 This problem may be caused by Antivirus software (such as
Innoculan)