Database Name

The name for the database that you want to appear in the database listing in PCC.

Note: The database name cannot be the same as an existing data source name (DSN).

Identifiers and Object Names

 

Location

This location must be on the same server to which you are connected (and where the database engine is running). Location must be formatted as though you are working directly at the server machine.

Dictionary Location and Data Directories

 

Bound

Indicates whether or not the database is bound. Binding a database prevents the DDFs or data files from being used in another database and prevents a data file from having two or more different table definitions within the same database.

For more information about bound databases, refer to Bound Database versus Integrity Enforced .

Interactions Between Btrieve and Relational Constraints

 

Create dictionary files

Specifies whether you want data dictionary files (DDF) created with the database. Dictionary files are required for relational (SQL) access to your data.

By default, the dictionary files and data files are created in the same location. You may specify different locations for these types of files after you create the database.

Typically, the only situation for which you would choose not to create DDF files is when you have an unnamed legacy database for which DDFs already exist, and you are now creating a database name for that database. Under these circumstances, the database engine links the new database name with the pre-existing DDFs.

Dictionary Location

 

Relational integrity enforced

Specifies whether integrity constraints (security, RI, and triggers) are enforced on the database. These constraints apply to Btrieve access to the data files as well as ODBC/SQL access.

Setting Up Referential Integrity

Interactions Between Btrieve and Relational Constraints

 

Create DSN

For ODBC access, you must set up a data source name (DSN) to refer to the database name. By default, the name of the new DSN is the same as the Database Name. Multiple DSNs may point to the same named database.

Note: The DSN that you are creating must be unique. You cannot create a database if the name that you specify for the database matches an existing DSN.

ODBC DSN Creation Options

 

Open mode

Allows you to specify one of several characteristics that go into effect when tables are opened through the specified DSN.

Table 1-6, DSN Open Modes and ODBC Connection Options,

 

Metadata

The database engine supports two versions of metadata, referred to as version 1 (V1) and version 2 (V2).

Metadata version is a property of the database and applies to all tables within that database. A database cannot use some tables with V1 metadata and others with V2 metadata. The DDFs of different metadata versions cannot interact.

Versions of Metadata in SQL Engine Reference

System Tables in SQL Engine Reference