New Database GUI Reference

New Database GUI Reference

The following image shows the dialog with which you create a new database. The table below the image describes the GUI objects. (See also To create a new database.)

Click an area of the image for which you want more information.

Figure 20 Create New Database Dialog

Table 10

Create New Database GUI Elements

Related Material

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

(back to Figure 20 )

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

(back to Figure 20 )

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

(back to Figure 20 )

Create dictionary files (if they do not exist)

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 preexisting DDFs.

Dictionary Location

(back to Figure 20 )

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

(back to Figure 20 )

Long Metadata (V2 metadata)

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

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.

SQL Grammar Support in ODBC Guide

System Tables in SQL Engine Reference

(back to Figure 20 )

Database Code Page

Specifies the code page property for the database. The default is “server default,” meaning the default operating system code page on the server.

See “Related Material” column for the section where this property is discussed fully.

Database Code Page

(back to Figure 20 )

Create 32-bit Engine 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.

The default is to create the DSN with an encoding translation option of “None.”

Note: The DSN that you are creating is a 32-bit Engine DSN. PCC cannot create 64-bit DSNs.

Use an ODBC Interface utility to create 64-bit DSNs (such as ODBC Administrator on Windows). Note that DSN names must be unique for their bitness. A 32-bit DSN and a 64-bit DSN can have the same name because their bitness differs.

DSN Setup and Connection Strings in ODBC Guide

Automatic in ODBC Guide

Additional Utilities

(back to Figure 20 )