
1-83
1 to 199
You attempted to modify a bound file, and the RI definition for
that file disagrees with the definition in the RELATE.DDF file.
You attempted an Insert, Delete, or Update operation that would
change a foreign key, if the file related to this file is out of sync
(an attempt to open or modify the related file would have
returned this same status code).
You attempted to create a file with the Replace option, and a
bound MicroKernel data file with the same name and location
already exists. However, the MicroKernel detected that the
existing bound file was out of sync (that is, an attempt to open
the existing file would have returned this same status code).
Note The same named database cannot exist on two servers on
the same network. So, if the intent is to move the dictionaries to
another server on the same network, one way would be to delete
the named database on the old server before creating the same
named database on the new server.
Check the RI constraints on your database. For information about
how to do this, refer to Pervasive PSQL User's Guide.
76: There is a conflict on the referenced file
An application attempted to perform an Update, Insert, or Delete
operation on an RI-controlled file that references another file. The
application cannot open the referenced file for RI checking because
it is already open in Exclusive mode. Wait until the referenced file is
closed or is opened in a mode other than Exclusive, and then retry
the operation. Refer to Advanced Operations Guide for more
information about RI.
77: The application encountered a wait error
This status code is obsolete in MicroKernel versions 7.0 and later.
This is an informative status code. You must retry the operation
yourself; the MicroKernel does not automatically retry the
operation. A client/server MicroKernel returns this status code in
one of the following situations:
The application specified a wait lock bias for an operation, but
another user has locked the requested resource.
Comentarios a estos manuales