Copyright: Copyright © 1982-2001 Pervasive Software Inc.     All Rights Reserved


Pervasive ODBC Engine DSN

Data Source Name: A name that identifies the data source.

For example: Personnel

Description: An optional description of the data in the data source.

For example: Hire date and salary history of all employees

The Options... button allows you to set the Pervasive file open mode.

Database

Database Name: The name that identifies the database.

The Create... button allows you to create or add new Database Names.

Tip

Engine DSNs created locally can be user or system DSNs, depending on how they are set up. The Pervasive ODBC Engine DSN must be a system DSN (not user DSN) to allow the service to connect via an ODBC client.

You can click the Test button when you complete the Pervasive ODBC Engine DSN dialog box to verify a successful connection.


Options

The open mode may be specified in the SQLSetConnect call options. It is in effect for the duration of a session. The open mode may affect whether a given action is valid or not.

Normal - permits shared read/write access. Integrity checks are performed when files are updated.

Read Only - permits only read operations on the file. Operations such as INSERT, UPDATE, and DELETE will fail. DDL statements are not permitted in this mode.

Accelerated - is the same as Normal mode except that certain transaction features are not in effect (e.g., file is not flagged as transactional). It provides improved response time when updating files but increases the chance that a crash could damage data integrity.

Exclusive - permits non-shared read/write access. No other task is permitted to open a file opened in this mode until that file is closed by the current task.


Create Database

Database Name: The name that identifies the database.

Integrity Enforced Select this check box to enforce integrity constraints, including security, referential integrity, and triggers.

Bound (DDFs created) Select this check box to bind the database.

Dictionary Location Enter the path and directory location where the data files are located. You may select a different location using the Browse... button.

Data File Locations The path and directory location(s) for the data files. You may add or remove locations using the Add... and Remove buttons.

Tip

If you choose to create a bound database, no other database can point to the same dictionary location specified.

 If you are creating a database that resides on a machine with the Server Engine, the dictionary location has to be local to the machine on which you are creating the database.

 If you are creating a database that resides on a a machine with the Workgroup or Workstation Engine, the dictionary location can be local to the machine on which you are creating the database, or the dictionary files directory on a remote server.

NetWare Users: If the database resides on a NetWare server, the dictionary location should look something like sys:\pvsw\demodata.

Windows NT Users: If the database resides on a Windows NT server, the dictionary location should look something like d:\pvsw\demodata.