Turns on workarounds that allow you to take full advantage of the ODBC driver with ODBC applications requiring nonstandard or extended behavior.
When this attribute is set in the configuration file, it is valid for all applications that connect to OpenAccess SDK. When you add this attribute in the connection string, it is set for that application connection only.
Refer to the OpenAccess SDK Client Reference for more information about connecting using a connection string.
Important: Each of these options has potential side effects related to its use. An option should only be used to address the specific problem for which it was designed.
2=Some applications incorrectly specify the ColumnSize/DecimalDigits when binding timestamp parameters. This option causes the driver to ignore the ColumnSize/DecimalDigits specified by the application and use the database defaults instead.
4=Microsoft Access uses the most recent native type mapping, as returned by SQLGetTypeInfo, for a specific SQL type. This option reverses the order in which types are returned, so that Microsoft Access will use the most appropriate native type.
32=Microsoft Access does require that the characters "DSN=" are returned by SQLDriverConnect in the connection string output parameter.
128=Workaround for Delphi. Delphi uses multiple connections when SQL_ACTIVE_STATEMENTS != 0. This workaround makes SQLGetInfo report 0 for SQL_ACTIVE_STATEMENTS. Delphi will use multiple statements within the same connection.
256=Workaround for ADO. This workaround causes BASE to return LongDataBuffLen value as strlen on SQL_LONGVARCHAR and SQL_LONGVARBINARY columns when SQLGetData is called with a bufferlength of 0.
1024=Workaround for ADO. OpenAccess drivers that support resultsets in procedures report Yes for the getInfo SQL_MULT_RESULT_SETS. ADO interprets this as if the last set of results has all of the output parameter data, in the same manner as SQL Server.
2048=Workaround for cursor library. The cursor library is still a 2x ODBC application and still uses the SQL_TIMESTAMP, not SQL_TYPE_TIMESTAMP. This is only a problem if the application is set to 3x ODBC compatibility.
4096=Workaround for Driver Manager bugs when handling UNICODE conversions.
8192=Workaround for Microsoft Access2000 when it calls SQLStatistics and getdata for column number 10 does not allow the null termination.
16384=Workaround to disable the base optimization if an application calls Prepare/Execute, then Prepare/Execute with the same sql base prepares the statement and does not treat it as a Prepare/Execute/Execute.
2=Some applications incorrectly specify the ColumnSize/DecimalDigits when binding timestamp parameters. This option causes the driver to ignore the ColumnSize/DecimalDigits specified by the application and use the database defaults instead.