 |
DSN-less ODBC connections
The c-tree ODBC Driver can be used without a DSN (data source name) by specifying the ODBC Driver Name rather than a DSN in the connection string, along with the desired options:
DRIVER=FairCom X ODBC Driver;keyword1=value1;…;keywordN=valueN;
The DRIVER specification above must be either “FairCom 32bit ODBC Driver” (for the c-tree Plus Driver) or “FairCom c-tree ODBC Driver” (for the c-tree V4 Driver). The Driver supports the following option keywords in the connection string.
Keyword
|
Supported Values (default value listed first)
|
Alignment
|
Default, 1, 2, 4, 8
|
AllowUpdates
|
No, Yes
|
CaseSensitive
|
Yes, No
|
ColumnOrder
|
Position, Name
|
CommEncryption
|
No, Yes
|
DataBuffers
|
64
|
DataDictionary
|
FAIRCOM.DB
|
DBQ
|
c:\otree
|
DebugCtree
|
No, Yes
|
DebugIndex
|
No, Yes
|
Files
|
395
|
GuestLogin
|
Yes, No
|
IndexBuffers
|
64
|
MaxColSupport
|
256
|
OEMtoANSI
|
No, Yes
|
Protocol
|
MultiUser, TCPIP, NETBIOS, SPX
|
Sectors
|
16
|
ServerName
|
FAIRCOMS
|
SpecialTypes
|
None
|
StringDataPad
|
Zeros, Spaces, NulTermSpaces
|
StringKeyPad
|
Default, Zeros, Spaces
|
These keywords correspond to the registry settings described in “Advanced - Registry Options”, with the following exceptions:
- ColumnOrder corresponds to the ColumnsOrderedBy registry setting.
- StringDataPad corresponds to the StringDataPadding registry setting.
- StringKeyPad corresponds to the StringKeyPadding registry setting.
- There are no supported connection string keywords for the ForceClose, KanjiConvert, and EnableFPUExceptions registry settings.
- The MaxRows setting can be used to limit the number of accessible rows, though there is no corresponding registry setting.
|
