Did this article resolve your question/issue?



Explanation of the ODBC Data Source parameters

« Go Back


TitleExplanation of the ODBC Data Source parameters
URL NameP116662
Article Number000155314
EnvironmentProduct: Progress 9.x, OpenEdge 10.x
Version: All supported versions
OS: All supported platforms
Database: All supported databases
Application: All supported applications
Other: ODBC Drivers
Question/Problem Description
Explanation of the ODBC Data Source parameters
What is the meaning of the various ODBC Data Source parameters ?
What are the definitions of the ODBC.INI tags ?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number

The definition of the ODBC.INI tags are as follows:

  • Driver: The data source specific library used by the Driver Manager.
  • DatabaseName: The name of the database used by this DSN.
  • PortNumber: The Network Service number the database server is listening for connections on.
  • HostName: The name of the host machine the database server is running on.
  • LogonID: The default user id for logon to the database server.
  • Password: The password for the default user id.
  • APILevel: A number indicating the ODBC interface conformance level supported by the driver:
    0 = None
    1 = Level 1 supported
    2 = Level 2 supported
  • ConnectFunctions: A three-character string indicating whether the driver supports SQLConnect, SQLDriverConnect, and SQLBrowseConnect. If the driver supports SQLConnect, the first character is "Y"; otherwise, it is "N". If the driver supports SQLDriverConnect, the second character is "Y"; otherwise, it is "N". If the driver supports SQLBrowseConnect, the third character is "Y"; otherwise, it is "N". For example, if a driver supports SQLConnect and SQLDriverConnect but not SQLBrowseConnect, the three-character string is "YYN".
  • CPTimeout: Time interval setting for Connection Pooling Timeout. Not support on UNIX.
  • DriverODBCVer: A character string with the version of ODBC that the driver supports. The version is of the form nn.nn, where the first two digits are the major version and the next two digits are the minor version.
  • FileUsage: A number indicating how a file-based driver directly treats files in a data source.
    0 = The driver is not a file-based driver. For example, a PROGRESS driver is a DBMS-based driver.
    1 = A file-based driver treats files in a data source as tables. For example, an Xbase driver treats each Xbase file as a table.
    2 = A file-based driver treats files in a data source as a catalog. For example, a Microsoft® Access driver treats each Microsoft Access file as a complete database.
  • SQLLevel: A number indicating the SQL-92 grammar supported by the driver:
    0 = SQL-92 Entry
    1 = FIPS127-2 Transitional
    2 = SQL-92 Intermediate
    3 = SQL-92 Full
  • UsageCount: Indicates driver libraries are in use. This value should not be modified.
  • ArraySize: A hint that can be provided to the ODBC driver with regards to how many records can be retrieved from the server at a time.
  • DefaultIsolationLevel: The default isolation level under which data will be accessed. Value could be any of :
          0 = READ COMMITTED
          1 = READ UNCOMMITTED
          2 = REPEATABLE READ
          3 = SERIALIZABLE
  • StaticCursorLongColBuffLen: The default size for retrieving sections of LVARBINARY data.

References to Written Documentation:

Progress Article(s):

P21252, How to set up and test the ODBC driver on Unix?

Last Modified Date5/8/2019 4:35 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.