Driver and DBMS Product Information (Magic xpa 3.x)
The utility connects to the data source selected and sends the SQLGetInfo function, which returns general information about the driver associated with the connection’s allocated handle.
To retrieve the same information, simply connect to the data source using Connect\Full Connect, and select Connect\SQLGetInfo with the specific fInfoType you want. The result is in the rgbInfoValue field in the result window.
SQL_DBMS_NAME = ACCESS
A character string with the name of the DBMS product accessed by the driver.
SQL_ODBC_VER = 03.51
A character string with the version of ODBC to which the Driver Manager conforms. The version is of the form ##.##, where the first two digits are the major version and the next two digits are the minor version. This is implemented solely in the Driver Manager.
SQL_DRIVER_NAME = odbcjt32.dll
A character string with the filename of the driver used to access the data source.
SQL_DRIVER_ODBC_VER = 03.51, major = 3, minor = 51
A character string with the version of ODBC that the driver supports. The version is of the form ##.##, where the first two digits are the major version and the next two digits are the minor version. SQL_SPEC_MAJOR and SQL_SPEC_MINOR define the major and minor version numbers. For the version of ODBC described in this manual, these are 2 and 0, and the driver should return “02.00". If a driver supports SQLGetInfo but does not support this value of the fInfoType argument, the Driver Manager returns ”01.00".
SQL_DRIVER_VER = 04.00.3513
A character string with the version of the driver and, optionally a description of the driver. At a minimum, the version is of the form ##.##.####, where the first two digits are the major version, the next two digits are the minor version, and the last four digits are the release version.
SQL_DBMS_VER = 01.00.0000
A character string indicating the version of the DBMS product accessed by the driver. The version is of the form ##.##.####, where the first two digits are the major version, the next two digits are the minor version, and the last four digits are the release version. The driver must render the DBMS product version in this form, but can also append the DBMS product-specific version as well. For example, “04.01.0000 Rdb 4.1".
SQL_DATabASE_NAME =
C:\gateways\ODBCSDK\SMPLDATA\ACCESS\SAMPLE
A character string with the name of the current database in use, if the data source defines a named object called “database.”
Note: In ODBC 2.0, this value of fInfoType has been replaced by the SQL_CURRENT_QUALIFIER connection option. ODBC 2.0 drivers should continue to support the SQL_DATabASE_NAME information type, and ODBC 2.0 applications should only use it with ODBC 1.0 drivers.
SQL_ACTIVE_CONNECTIONS = 64
A 16-bit integer value specifying the maximum number of active connection handles that the driver can support. This value can reflect a limitation imposed by either the driver or the data source. If there is no specified limit or the limit is unknown, this value is set to zero.
SQL_ACTIVE_STATEMENTS = 0
A 16-bit integer value specifying the maximum number of active statement handles that the driver can support for a connection handle. This value can reflect a limitation imposed by either the driver or the data source. If there is no specified limit or the limit is unknown, this value is set to zero.
SQL_ODBC_API_CONFORMANCE = Level 1 Supported
A 16-bit integer value indicating the level of ODBC conformance:
SQL_OAC_NONE = None
SQL_OAC_LEVEL1 = Level 1 supported
SQL_OAC_LEVEL2 = Level 2 supported
SQL_SEARCH_PATTERN_ESCAPE = \
A character string specifying what the driver supports as an escape character that permits the use of the pattern match meta-characters underscore (_) and percent (%) as valid characters in search patterns. This escape character applies only for those catalog function arguments that support search strings. If this string is empty, the driver does not support a search-pattern escape character. This fInfoType is limited to catalog functions.
SQL_SERVER_NAME = ACCESS
A character string with the actual data source-specific server name; useful when a data source name is used during SQLConnect, SQLDriverConnect, and SQLBrowseConnect.
