| **Navigation:**  SQL Drivers > Pervasive SQL Accelerator Driver >====== Pervasive SQL Connection Information and Driver Configuration--File Properties ====== | [[pervasive sql import wizard login dialog.htm|{{btn_prev_n.gif|Previous page}}]][[coming future.htm|{{btn_home_n.gif|Return to chapter overview}}]][[b2j48dn.htm|{{btn_next_n.gif|Next page}}]] |
|  ||

Typically, you add Pervasive SQL support to your application by importing the table definitions into your Clarion Data Dictionary. The Import Wizard automatically fills in the **File Properties** dialog with default values based on the imported item. However, you can use the **Owner Name** field in the **File Properties** dialog to further configure the way the Pervasive SQL Driver accesses the data.

Pervasive SQL allows some information in addition to the database identification in the **Owner Name **field. This information appears alternatively as:

**Database[,Owners;Switches]**

or

**DDF=DDFPath[|Datapath][,Owners;Switches]**

Where //Database //is the name of a Pervasive SQL database. //DDFPath //is a path to a set of DDF (Btrieve data dictionary) files. //Datapath //is the path to the corresponding data files. If omitted, //Datapath //defaults to //DDFPath//. //Owners //is a comma separated list of names to try when opening encrypted Btrieve files. If a name contains a comma or space, it must be surrounded by single quotes. //Switches //is a semicolon separated list of assignments. Valid switches are:

**CREATEDDF=[0|1|2]**

Where //0 //creates a new DDF file, //1// replaces the existing DDF file, and //2// removes the existing DDF File.

{{notebox.jpg|NoteBox.jpg}}

**The CREATEDDF switch is provided primarily for use during initial installation to allow you to build new DDF files. You should never use this switch for existing databases.**