Pervasive.SQL Error Class (20482 - 20575)

The DataFlex error system defines several classes of errors: user, system and utility errors. The DataFlex Pervasive.SQL driver adds an error class to the DataFlex error classes and introduces the following errors.

20482 — Invalid Integer Length

Integer fields are only supported to have a size of 1, 2, or 4 bytes. Any other length will trigger this error.

20483 — Can't Get Stat Information

Whenever the driver is opening a Pervasive.SQL table, it tries to get information about that table from the Pervasive.SQL engine it is connected to. This error indicates an error during that process.

20484 — Index Structure Mismatch

One of the following conditions is true:

The Pervasive.SQL table has indexes that are not present in the DDF tables.
The index definitions described in the DDF tables do not match the index definition of the Pervasive.SQL table.

20485 — Index Segment Field Structure Mismatch

An index segment described in the DDF table does not match the offset and/or the length of the actual segment in the Pervasive.SQL table.

20486 — No Index for Record Identity

A table that is using recnum support has no index for the recnum field.

20487 — Invalid Character in Path

The driver detects an invalid character being used in the path for a table. Pervasive.SQL does not support the use of spaces in a path, for example.

20488 — Field Invalid Type

An internal routine has been called with a field type that is invalid for DataFlex.

20489 — Unsupported Date Type

A date field is being accessed from within a DataFlex program, but the Pervasive.SQL field type is not a date.

20490 — Can't Find Segment Field

A record from INDEX.DDF is pointing to a non-existent field in FIELD.DDF, or the field it is pointing to is not part of the target table.

20491 — Invalid Driver Function Call

The Call_Driver command is being executed with an illegal function number.

20492 — File Exists

The driver is trying to create a Pervasive.SQL table that already exists somewhere in a directory reachable through the DFPATH environment setting.

20493 — Can't Delete File

An error occurred when a Pervasive.SQL table was being created and the driver can't delete the created table for cleanup.

20494 — Pervasive.SQL Path Too Long

The maximum length of a path for a Pervasive.SQL table accessed through this driver is 255 characters. This error indicates that more than 255 characters are being used.

20495 — DDF File Entry Not Found

The driver can't find the table specified in FILE.DDF. Check that the correct table is being accessed and that the driver is using the right DDF tables.

20496 — Can't Get Temp Handle

The driver can’t find a free file number to temporarily open a new table under when converting a table to Pervasive.SQL from another format.

20497 — Root Name Too Long

This error can be generated when the new rootname of a converted table has become too large to fit into the rootname slot of a file-list entry. The maximum length of a rootname is 40 characters. If your current rootname includes a path, remove the path and set the DFPATH so the table can be reached through DFPATH.

20498 — Can't Convert Inside Transaction

Table conversions can only take place outside the scope of a database transaction.

20499 — Recnum Has To Be Last In Index

This error can occur if a table is being converted without recnum support and the recnum field is being used as a segment in an index while that segment is not the last segment of that index. The driver will not instruct Pervasive.SQL to include the recnum field; instead it will mark the index to allow duplicates (the usual reason the recnum field is included in indexes).

20500 — Invalid Overlap

The conversion function can't find the field that the start or endpoint of an overlap field is pointing to.

20501 — Invalid INT Fieldtype

This error is generated when the type defined in an INT file for a field does not match one of the standard DataFlex field types. Supported field types are ASCII, BCD, DATE, OVERLAP, TEXT and BINARY.

20502 — License Expired

This error indicates that the expiration date of your DataFlex for Pervasive.SQL license has passed. Contact your distributor or Data Access Corporation.

20503 — Logical Value Out Of Range

Pervasive.SQL logical fields only have values between 0 and 255. In DataFlex, this field is being treated like a BCD field.

20504 — Invalid Field Name

An invalid field name has been used. The driver will correct illegal characters automatically.

20505 — Invalid Record Identity

The record-identity property of a table is being set to a value outside the range of valid field numbers or to a field that cannot be the record-identity field.

20506 — Invalid Field Type Combination

This error indicates that the internal field type conversion table could not convert the DataFlex field type into a valid Pervasive.SQL field type. This should never happen.

20507 — Can't Change Length of Static Data Type

This error is generated whenever the length is changed for a field connected to a Pervasive.SQL field type that has a static length, such as date or time field types.

20508 — Unsupported Pervasive.SQL Field Type

This error is generated whenever the driver has to deal with a field type it does not support.

20509 — Duplicate Field Name

A field already exists with the name of the new field.

20510 — Invalid Type for Offset

Set whenever the offset of a field that is not an overlap field is set — this error will be generated.

20511 — Invalid Offset Value

This error is generated when setting the offset would cause the overlap to lie past the end of the record.

20512 — Invalid Index Number

An invalid index number was passed to the driver.

20513 — Invalid Segment Number

An invalid segment number was passed to the driver.

20515 — Owner Name Too Long

The maximum length of the owner name of a table is 8 characters. Whenever a larger string is being passed, the driver will generate this error.

20516 — Owner Set Within Restructure

An owner name can only be set outside a restructure operation. This error indicates it was done within a restructure operation.

20517 — Err Invalid Owner Flags

An invalid flag was passed when setting the owner name of a table.

20518 — Can't Delete File — Read-only

The driver tried to delete a table and received an error that the table is marked as read-only.

20519 — Can't Delete File — Invalid Path

The driver tried to delete a file and is using an invalid path. This should never happen.

20520 — Field Name Adjusted

The name of a field has been truncated because its length exceeded the maximum number of characters allowed for a Pervasive.SQL field name, which is 20 characters.

20522 — Can't Create Temp File

When finishing a restructure operation, the driver first creates the file under a new temporary filename, then renames the original file to another temporary filename and finally renames the first temporary filename to the original name. It uses a random-number generator to get a temporary filename. When it can’t get a temporary filename, it declares this error.

20523 — Can't Find ACS

The driver is trying to load the ACS specified using the driver configuration file or the ACS keyword, but it can’t find the ACS.

20524 — Can't Find Upper ACS

The driver is trying to load the ACS specified using the driver configuration file or one of the ACS keywords, but it can’t find the ACS.

20525 — Can't Open ACS

The driver is trying to open the ACS specified using the driver configuration file or the ACS_UPPER keyword, but it can’t open the ACS.

20526 — Invalid ACS

The format of the ACS does not comply with the expected format. Read the "Using Alternate Collating Sequences in Pervasive.SQL" documentation or refer to the documentation that came with your Pervasive.SQL engine.

Link: Using Alternate Collating Sequences in Pervasive.SQL

20527 — Maximum Number of Segments Exceeded

The Pervasive.SQL table you are working with has no more index segments available. Every Pervasive.SQL table can have a maximum number of segments defined. This number of segments is independent of the number of indexes. The number of segments that can be used depends on the page size of a Pervasive.SQL table. The following table gives the maximum number of segments available per page size:

Page Size	Segments
512	8
1024	23
1536	24
2048–3584	54
4096	119

20528 — DDF Indexes Not Complete

A Pervasive.SQL index contains more segments than are defined in the DDF table for that index.

20529 — DDF Index Segments Not Complete

An index in a Pervasive.SQL table is found which is not present in the DDF tables.

20530 — Stat ACS Structure Mismatch

The result of a Pervasive.SQL Stat operation does not match the number of ACSes expected.

20531 — Invalid Transaction Type

An invalid transaction type is being set. Valid types are NONE, EXCLUSIVE, and CONCURRENT.

20532 — Cannot Change Transaction Type While Active

The driver was requested to change the transaction type while a transaction is active.

20533 — Invalid Registration File

This error indicates that the information in your registration file is invalid. Please re-enter the registration code for the product.

20534 — File Has No Fields

This error will be triggered when a table with no fields defined is opened. This may be caused when no record can be found in FIELD.DDF that refers to the table being opened.

20535 — Invalid Configuration Keyword

This error indicates that an invalid keyword has been used in the DFBTRDRV.INT configuration file.

20536 — Length of Date Field Can't Be Changed

This error will be generated when an application tries to change the length of a field whose type has been set to date. Date fields have a fixed format.

20537 — Can't Find DF4BTR Recnum Field

When the DATAFLEX_FOR_BTRIEVE flag has been set to TRUE for a table, the driver will search for a field called DATAFLEX_RECNUM_ONE in the table, which will represent the recnum. This error indicates that this field cannot be found in the field list.

20538 — Cannot Open Cachefile For Write

This error is generated when structure caching has been enabled (USE_CACHE 1), cache error reporting has been enabled (REPORT_CACHE_ERRORS 1), and an error occurs while trying to create the cache file.

20539 — Cannot Write To Cachefile

This error is generated when USE_CACHE 1 and REPORT_CACHE_ERRORS 1 are set and an error occurs while writing the cache file.

20540 — Cannot Read From Cachefile

This error is generated when USE_CACHE 1 and REPORT_CACHE_ERRORS 1 are set and an error occurs while reading the cache file.

20541 — Cannot Read Signature From Cachefile

This error is generated when USE_CACHE 1 and REPORT_CACHE_ERRORS 1 are set and an error occurs while reading the signature from the cache file.

20542 — Cannot Open Cachefile For Read

This error is generated when USE_CACHE 1 and REPORT_CACHE_ERRORS 1 are set and an error occurs while opening the cache file for read.

20543 — Cannot Close Cachefile

This error is generated when USE_CACHE 1 and REPORT_CACHE_ERRORS 1 are set and an error occurs while closing the cache file.

20544 — Invalid INT Fieldtype BTR

Valid values for FIELDTYPE_BTR are: STRING, INTEGER, IEEE, DATE, TIME, DECIMAL, MONEY, LOGICAL, NUMERIC, BFLOAT, LSTRING, ZSTRING, NOTE, UNSIGNED, AUTOINCREMENT, NUMERIC_STS and NUMERIC_SA.

20545 — Invalid INT Fieldtype AUX

Valid values for FIELDTYPE_AUX are: LSTRING2 and DFBCD.

20546 — Cannot Find Unique Fieldname

The driver could not create a unique field name when creating a field.

20547 — Invalid Fieldtype For GetString

The field type of the field for which the string value is being requested is not supported for getting a string value.

20548 — Invalid Recnum Method

An invalid value has been specified for the RECNUM_METHOD setting of DFBTRDRV.INT. Valid values are GET_POSITION, POSITION_BLOCK, DOUBLE_CHECK and AUTO_CONFIG.

20549 — Recnum Mismatch

This error is generated when the RECNUM_METHOD has been set to DOUBLE_CHECK and the values obtained from the GET_POSITION and POSITION_BLOCK methods do not match.

20552 — Invalid Cachefile Version

This error is generated when USE_CACHE 1 and REPORT_CACHE_ERRORS 1 are set and an error occurs while reading the cache file due to an unexpected cachefile version.

20554 — Cannot Rename File

This error is generated when the driver failed to rename a file while restructuring a file.

20555 — Invalid Zerofile Method

An invalid value for the ZEROFILE_METHOD of DFBTRDRV.INT has been specified. Valid values are CREATE, FALLBACK and DELETE.

20556 — Cachefile Expired

This error is generated when USE_CACHE 1 and REPORT_CACHE_ERRORS 1 are set and the cachefile has expired or cannot be used.

20557 — Cannot Find Cachefile

This error is generated when USE_CACHE 1 and REPORT_CACHE_ERRORS 1 are set and an error occurs while trying to locate the cache file.

20558 — Invalid Character Set

This error is generated when an invalid character set is specified in DFBTRDRV.INT.

20559 — Cannot Open Logfile

This error is generated when a LOGFILE_PATH has been specified and the specified file cannot be opened.

20560 — Length Of Timestamp Field Can't Be Changed

This error is generated when an application tries to change the length of a BTR_TIMESTAMP_TYPE (type 20) field.

20561 — Single Recnum Index Not Allowed

This error is generated when an application tries to define an index with RECNUM as the only field segment in the index.

20562 — Incompatible Pos Sign Detected

This error is generated when the driver reads a numeric value from the Pervasive.SQL table which has a different value for the positive sign than the value specified by COMP3_SIGN_POS in DFBTRDRV.INT. (If no COMP3_SIGN_POS is specified, the default value of 15 (Hex 0x0F) will be used.)

This error message can be turned off by specifying in DFBTRDRV.INT:

DETECT_INCOMPATIBLE_SIGN_POS 0

20563 — File DDF Full

This error is generated if no new XF$ID value in FILE.DDF can be generated. New XF$ID values are generated by scanning FILE.DDF and taking the first available free XF$ID value.

20564 — Field DDF Full

This error is generated if no new XE$ID value in FIELD.DDF can be generated. New XE$ID values are generated by scanning FIELD.DDF and taking the first available block of consecutive free XE$ID values where the fields to add will fit.

20565 — Number Cannot Be Negative

This error is generated if the application tries to store a negative value to a numeric field type that does not allow negative values.

20566 — Owner Name Not Valid

The table cannot be opened while the owner name is not valid for access to the table; this means the table is protected against both reading and writing.

20567 — Restructure Not Allowed

This error indicates that the table on which a restructure operation is requested does not allow that. Reasons for this might include:

The DDF tables are read-only.
The table contains incompatible field types.

The extra error text will indicate the source of the problem.

20568 — Invalid Nullable Column

This error is given when a field is marked as nullable, but the structure for storing the nullable information is not found or is incorrect.

20569 — One Or More Indexes Not Created

This error indicates that one or more indexes could not be created during a restructure operation. There can be various reasons why an index cannot be created (for example, because the index contains duplicate entries for an index that is supposed to be unique). Check the table after the restructure operation has completed to see which indexes were not created.

20570 — Mixed NOTE and LONGVAR Type In Record

This error indicates that within one table, fields of both the NOTE and LONGVAR field types have been found. This is an illegal structure.

20571 — Longvar Data Too Large For Record

The data that is currently placed in the record buffer cannot be saved because the total length of the record is too large for the record or the communication buffer size. By default, a record cannot be larger than 64 KB.

20572 — Incompatible Database Engine Version

This error indicates that the Pervasive.SQL Database Engine this driver is used with is not compatible with this driver. You need to upgrade your Pervasive.SQL Database Engine to a later version to be able to work with this driver.

20573 — Invalid Text Type

The TEXT_TYPE setting in DFBTRDRV.INT has an invalid value.

20574 — Invalid URI

A URI with an illegal format has been specified. Allowed syntax for URIs can be found in the Pervasive.SQL documentation.

20575 — Cannot Open DDFs

The DDFs are opened when the first table is opened. This error will be raised if the DDFs cannot be opened in DATABASE_MODE. The extra error information will specify the PSQL status code and the URI used in the open.