-9100 to -9000

---

Utilities Status Codes

This section lists status codes returned by the Pervasive.SQL utilities. Should you encounter an error code in the range -9100 to -9000 that is not listed in this section, record the steps taken to get the particular error you received and notify Technical Support at Pervasive Software.

-9000: The index key numbers in the Btrieve file do not match index key numbers defined in the DDF

This status code can appear when you are using Table Designer. If you save your table design with Table Designer in linked mode, the index key numbers in the Btrieve data file will be renumbered. Your application may not be able to access its data. Index keys defined in DDFs are numbered sequentially starting with zero. Index keys used in a Btrieve file may be any unique positive number chosen by the application developer.

An alternative to creating index keys with Table Designer is to create them with an SQL statement. The SQL statement assigns the next available index key number rather than renumbering the keys. An example helps clarify this.

Suppose you have the following index keys defined. The keys match by column type.

Index Keys in Btrieve Data File	Index Keys in DDF
0 2	0 1

If you were to add another index key with Table Designer in linked mode, the following would result:

Index Keys in Btrieve Data File	Index Keys in DDF
0 1 2	0 1 2

The keys in the Btreive data file are renumbered.

If you were to add another index key with an SQL statement, the following would result:

Index Keys in Btrieve Data File	Index Keys in DDF
0 2 3	0 1 2

The newly added key is assigned number 3 in the Btrieve data file since key number 2 is already used.

Note that unlinked mode also renumbers index keys. For example, suppose you have keys 0 and 2 in your Btrieve data file, and key 0 in your DDFs. If you add another index key in unlinked mode, the DDFs keys get renumbered to 1 and 3. Use SQL statements instead of Table Designer if you want to avoid renumbering index keys.

-9003: The Btrieve file has index keys defined but no index keys are defined in the DDF

This status code can appear when you are using Table Designer. If you save your table design with Table Designer in linked mode, the index key numbers in the Btrieve data file will be renumbered. Your application may not be able to access its data. Index keys used by SRDE are numbered sequentially starting with zero.

To prevent the index key numbers in the Btrieve data file from being renumbered, switch Table Designer to unlinked mode, then save your table design. Unlinked mode affects only the DDF files and not the Btrieve data files. See To change Table Designer mode in Pervasive.SQL User's Guide.

Note that unlinked mode renumbers index keys in the DDFs. For example, suppose you have keys 0 and 2 in your Btrieve data file, and you add two keys in unlinked mode. The DDFs keys get renumbered 1 and 3. Use SQL statements instead of Table Designer if you want to avoid renumbering index keys.

-9004: The DDF has index keys defined but no index keys exist in the Btrieve file

This status code can appear when you are using Table Designer. If you save your table design with Table Designer in linked mode, your application will still be able to access its data. You may notice a performance difference because your Btrieve application will have index pages.