User`s guide

1-60
Status Codes
 When accessing a file on a server, ensure that you have FILE
SCAN rights to the directory in which the file resides.
Occasionally, a corrupt key can cause this status code. Drop the
key, then add it again.
 This error code may also be returned when the file
DBNames.CFG has been removed (for example, by the Pervasive
PSQL cleanup utility) and old Data Source Names (DSNs)
which reference that file are not removed from the ODBC
configuration.
 You attempted to open a local file with a Workgroup engine that
isn’t the designated Gateway engine for the file. Go to the
directory where the file you attempted to open resides. Check to
see if the
~pvsw~.loc in that directory is flagged read only. If it
is, change it to read-write.
 You may have a Status 12 returned and see X$FILE.DDF for the
file name in your DDFs.
 If the file.ddf is examined with a Btrieve utility, the location
name for the dictionary files will be x$file.ddf, x$field.ddf,
x$index.ddf, instead of the standard file.ddf, field.ddf,
index.ddf. An unsupported DDF Creation utility called
DDL Services (DDLSVCS.DLL) created the DDFs. DDL
Services has a known bug that causes the system table to be
populated with incorrect data. .
 You may get Status 12 when a file with a filename or path with
embedded spaces is opened on certain Windows 32-bit
platforms. Btrieve data files can be accessed using long names
but long names cannot be used for other files.
 To Enable Embedded Spaces in Pervasive.SQL 2000i or later:
1 Start Pervasive PSQL Control Center (see Starting PCC on
Windows in Pervasive PSQL User's Guide).
2 Expand the nodes for Pervasive PSQL (click the plus (+) sign).
3 Expand the Local Client node.
4 Right-click MicroKernel Router then click Properties. Login if
prompted.
5 Click Application Characteristics in the Properties tree.
6 Click Embedded Spaces (a check mark indicates that the option
is enabled).