Highlights for the current release of the ODBC drivers:

• Added ability to register a callback routine to receive notification of connection failover events.
  
• Changed the default value of the data source configuration option “Microsoft Transaction Server (MTS) Support” to be disabled. The check box for this option in the data source configuration form will now have a check mark in it by default. Enabling MTS support causes problems in ‘dblinks’ and ‘connection failover’ even if MTS is not used. Changing the default value to disabled will help reduce support calls. This change is not reflected in the online documentation file for the ODBC driver. The documentation will be corrected in the next release.
  
• Fixes for 18 bugs (11 P2's, 7 P3's)

Summary of Bug Fixes:

• Fixed data loss problem when calling SQLGetData for large objects and using a data type of SQL_C_DEFAULT. One byte was being lost for each call to SQLGetData. (Bug2847708)
• Fixed memory leak which happened each time the driver was loaded and unloaded in a process. (Bug2827429)
• Fixed an error in row counting wherein setting the SQL_ATTR_MAX_ROWS attribute with SQLSetStmtAttr to a value greater than one but less than the number of rows in the result set resulted in a premature SQL_NO_DATA status being returned, depending on the setting of SQL_ROWSET_SIZE. (Bug2799065)
• Fixed MS Visual Basic crash when processing ‘CREATE PROCEDURE’ statements that are around 4K in length. (Bug2786533)
• Fixed access violation when a NULL pointer was passed for the username or password on SQLConnect. (Bug2776239) 
• Driver no longer downgrades cursor if an aggregate function is present in the WHERE clause. (Bug2766470) 
• Queries that included LONG or LOB on a STATIC cursor were incorrectly being downgraded to a KEYSET cursor. (Bug2763894) 
• The correct column size of TIMESTAMP columns is now returned from SQLDescribeCol. (Bug2756264) 
• Driver no longer crashes when handling procedure calls with more than 2000 parameters. (Bug2755525) 
• CRLF in procedure call escape sequence no longer results in “syntax error” or access violation. (Bug2735674)
• Fixed a memory leak which would show up when executing multiple statements over a period of time. (Bug 2689837) 
• Fixed a parsing problem to recognize the "%" symbol following the escape character "\". (Bug2689223) 
• Fixed memory leak when using “select distinct”. (Bug2685365) 
• Forced SQLSetPos and SQLBulkOperations UPDATE operations to use the data size from the database rather than the buffer size specified by the application when that size is over 4000 and the metadata size is smaller. This prevents the Oracle engine from mistakenly thinking the application is attempting to insert LONG data. (Bug 2683435) 
• Fixed a problem for a function call without any argument and returning a ref cursor as its left-value. (Bug2680912)
• Fixed interoperability support statement in release notes. (Bug2657891)
• Fixed a problem in parsing ODBC escape sequence tokens. (Bug2643179)
• Support values of 0 or two to indicate a negative sign in the SQL_C_NUMERIC structure. The Microsoft ODBC 3.0 programmers reference manual states that a value of 2 is used to indicate a negative value, however, the 3.51 documentation states a value of 0. (Bug2511887)

Updated 28-March-2003