ODBC Connection Information and Driver Configuration--File Properties

Typically, you add SQL support to your application by importing the SQL or ODBC table, view, and synonym 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, there are several fields in the File Properties dialog you can use to further configure the way the ODBC Accelerator Driver accesses the data.  These File Properties fields, and their uses are described below.

Owner Name

Typically, the Import Wizard places the SQL database connection information (Host, Username, Password, etc.) in the Owner Name field.

Some backend databases may require additional connection information which you can supply in the Owner Name field.  This information follows the password and is separated by semicolons, using the syntax: keyword=value;keyword=value. 

For example, when accessing a Sybase database with the ODBC driver, this would appear as:

DataSource,UserID,PassWord,DATABASE=DataBaseName;APP=APPName

Consult your SQL Server's documentation for information on these keywords, their uses and effects.

ODBC Key Configuration--Key Properties

Typically, you add SQL support to your application by importing the SQL or ODBC table, view, and synonym definitions into your Clarion Data Dictionary.  The Import Wizard automatically fills in the Key Properties dialog with default values based on the imported item.  However, there are some fields in the Key Properties dialog you can use to further configure the way the ODBC Accelerator Driver accesses the data.  These Key Properties fields are described below. where clauses that are invalid for the backend server.

External Name

READONLY

Adding the READONLY switch to the External Name tells the ODBC driver not to insert the field when the record is added.  This is necessary for certain backends (such as Watcom) that do not allow autoincrementing key fields to be set to null.  Some backends do not allow autoincrementing key fields to be set to null, but they fail to advise the ODBC Accelerator Driver of this restriction.  The READONLY switch lets you manually advise of the restriction.

ODBC Column Configuration--Field Properties

Typically, you add SQL support to your application by importing the SQL or ODBC table, view, and synonym definitions into your Clarion Data Dictionary.  The Import Wizard automatically fills in the Field Properties dialog with default values based on the imported item.  However, there are some fields in the Field Properties dialog you can use to further configure the way the SQL Accelerator Driver accesses the data.  These Field Properties fields are described below.

External Name

NOWHERE

Adding the NOWHERE switch to the External Name tells the ODBC driver to exclude the field from any where clauses it sends to the backend server.  This is necessary for certain backends when WATCH is in effect.  Some backends do not allow certain data types in a where clause, but they fail to advise the ODBC Accelerator Driver of this restriction.  The NOWHERE switch lets you manually advise of the restriction when WATCH causes the ODBC driver to generate.