
1-57
1 to 199
The operation encountered an end-of-file boundary or tried to
read past a file boundary (end-of-file or start-of-file).
In a Get Next Extended, Get Previous Extended, Step Next
Extended, or Step Previous Extended operation, the number of
records satisfying the filtering condition is less than the number
of specified records to be returned, and the reject count or filter
limit has not been reached.
When reading a file in ascending order according to an index
path, the MicroKernel has already returned the last record in that
index path. When reading a file in descending order according to
an index path, the MicroKernel has already returned the first
record in the index path.
When using the Get By Percentage operation, either the value
supplied for the percentage is too high—it exceeds 10,000
decimal (0x2710)—or the file contains no records.
When using the Get operation using ActiveX Data Control, this
error will occur only after the application is compiled and
deployed. This error will not occur at design time during
development. The error results from a missing MSDADC.DLL
on the deployment machine. Make sure to include this file
(MSDADC.DLL) in your installation script. This file is a
Microsoft MDAC (Microsoft Data Access Component) file.
Note Please see our Pervasive PSQL Knowledge Base for new
and updated articles on Btrieve ActiveX Controls. You can access
the Knowledge Base at the Pervasive Software website.
10: The key field is not modifiable
During an Update operation, the application attempted to modify a
key field that cannot be modified by definition.
11: The specified filename is invalid
The MicroKernel returns this status code in the following situations:
The specified filename does not conform to file naming
conventions or the pathname is invalid. Make sure the filename
or pathname is valid for the environment.
If operating in the client/server environment:
Comentarios a estos manuales