|
<< Click to Display Table of Contents >> ODBC driver connection settings |
![]() ![]()
|
To configure the way tables in an ODBC data source are created, sorted, and handled, choose an ODBC driver connection as the driver name on the Configuration page of the BDE Administrator or create or select an alias on the Databases page that uses an ODBC driver.
To change a setting, highlight the desired configuration parameter. Delete the old value and enter a new one in the appropriate text box. You can only change parameters WITHOUT bold labels.
In the following table, Parameters lists all tracked parameters for the selected driver type, and their current settings. When the driver is first installed, all values are set to their defaults.
Description briefly notes the purpose of the highlighted parameter.
Parameter |
Description |
||||||||
VERSION |
Internal version number of the ODBC driver. Do not modify. |
||||||||
TYPE |
For drivers, this parameter is Server. It is uneditable. |
||||||||
DLL |
The name of the driver's 16-bit Dynamic Link Library (*.DLL). Default: IDODBC16.DLL |
||||||||
DLL32 |
The name of the driver's 32-bit Dynamic Link Library (*.DLL). Default: IDODBC32.DLL |
||||||||
ODBC DRIVER |
The ODBC driver used to connect the workstation to the target ODBC server. |
||||||||
DRIVER FLAGS |
Internal product-specific flag. Do not change without direct instructions from Borland support personnel. |
||||||||
DATABASE NAME |
The drive, path, and file name to access. |
||||||||
USER NAME |
Default name for accessing the ODBC server. |
||||||||
ODBC DSN |
The name of the ODBC data source to which this alias will connect. Must be the same as the ODBC data source you named when you created the ODBC driver connection. |
||||||||
OPEN MODE |
Mode in which the ODBC driver connection opens the database. Can be READ/WRITE or READ ONLY. Default: READ/WRITE |
||||||||
LANGDRIVER |
Language driver used to determine table sort order and character set. |
||||||||
SCHEMA CACHE SIZE |
Number of SQL tables whose schema information will be cached. Can be any whole number from 0 to 32. Default: 8 |
||||||||
SCHEMA CACHE DIR |
Specifies the directory in which the local schema cache is stored. Used when ENABLE SCHEMA CACHE is TRUE to cache schema locally when tables reside on an SQL server. |
||||||||
SQLQRYMODE |
Method for handling queries to SQL data. Can be NULL (blank setting), SERVER, or LOCAL. [more] |
||||||||
SQLPASSTHRU MODE |
Specifies whether or not the BDE application will be able to access the SQL server via desktop queries and passthrough SQL queries in the same database alias connection. Can be NOT SHARED, SHARED AUTOCOMMIT, or SHARED NOAUTOCOMMIT. [more] Default: SHARED AUTOCOMMIT |
||||||||
TRACE MODE |
A numeric value (bit mask) specifying how much trace information to log. The Windows OutputDebugString call is used to output the requested information to the debug window. The following table shows which information is logged based on bit settings: Bit Settings Logged Information 0x0001 prepared query statement 0x0002 executed query statements 0x0004 vendor errors 0x0008 statement options (that is: allocate, free) 0x0010 connect / disconnect 0x0020 transaction 0x0040 BLOB I/O 0x0080 miscellaneous 0x0100 vendor calls |
||||||||
ENABLE SCHEMA CACHE |
Specifies whether the BDE caches table schema locally for tables residing on SQL servers. This enhances performance for table opens. Set SCHEMA CACHE DIR to the directory in which the local cache is stored. |
||||||||
SCHEMA CACHE TIME |
Specifies how long table list information will be cached. (In the BDE, table information is cached when you call either DbiOpenTableList or DbiOpenFileList.) Setting this value can increase performance for table and file list retrieval. Possible modes and their meanings are listed here.
Default: -1 |
||||||||
BATCH COUNT |
Specifies the number of modified records to be included in a batch before auto-committing. In this way you can adjust the size of a batch to accommodate server transaction logs that are not big enough to handle the whole batch. In the BDE, you can override this value by setting the database property, dbBATCHCOUNT. See Borland Database Engine Online Reference (bde32.hlp) Default: The number of records that can fit into 32 KB |
||||||||
MAX ROWS |
Specifies maximum number of rows that the SQL driver will attempt to fetch for every SQL statement sent to the server. [more] |
||||||||
ROWSET SIZE |
Specifies the number of rows to retrieve from the server in a single fetch, and the number of records to insert at a time when using DbiWriteBlock. This setting isn't supported by all ODBC drivers. |
||||||||
ENABLE BCD |
Specifies whether BDE translates numeric and decimal fields into floating point values or binary coded decimal (BCD) values. BCD values eliminate the rounding errors associated with floating point math (such as a 3 * (2/3) resulting in 2.00000000001). When ENABLE BCD is set to TRUE, DECIMAL and NUMERIC fields are converted to BCD for ODBC drivers. |
||||||||
BLOBS TO CACHE |
Determines how many BLOBs will be cached on the client. Applications that deal with fetching dead BLOBs using dead table opens or queries can set a limit on the number of BLOBs to cache depending on the resource available on the client. |
||||||||
BLOB SIZE |
Determines the fetch buffer size for dead BLOBs. Applications that deal with dead BLOBs using dead table opens or queries or batchmoves can set a maximum limit on the size of BLOBs to fetch. Setting this parameter to 64 means your application can fetch BLOBs of up to 64K. This parameter does not apply to live table opens. Default Value: 32, Range : >32 and <1000. |