91) 1/21/2012 811347 Developer's Guide for Troubleshooting Data Access Applications
(811347) - During the development and test phases of any software solution, you may experience problems. These problems might be related to the code or to the configuration that you use. Typically, most of these problems are caught during the development and... 92) 2/2/2012 314639 BUG: Access Violation Occurs When You Open a Recordset with a Different Lock Type
(314639) - If you close a recordset, and then reopen the recordset with a different lock type, an access violation may occur. 93) 2/5/2012 314635 FIX: "Catastrophic Failure" Error Message When You Use adPromptAlways to Connect to SQL Server 2000
(314635) - When you use the adPromptAlways constant to open a connection to SQL Server 2000, the user receives the following error message: 'Run time error '-2147418113 (8000ffff)': Catastrophic Failure'. This problem occurs when you use a trusted connection to... 94) 2/7/2012 312495 FIX: SQLManageDataSources Fails When Connection Pooling Is Turned On at Process Level
(312495) - When you turn on connection pooling at the process level and call the SQLManageDataSources function to configure a file data source name (DSN), you may receive the following error: General error: Invalid file dsn 'C:\Program Files\Common... 95) 2/8/2012 308262 FIX: Access Violation Occurs on the Filter Property in ADO
(308262) - An access violation may occur if you try to access the Filter property of an ActiveX Data Objects (ADO) Recordset object on a multi-processor computer under heavy load. 96) 2/8/2012 303446 FIX: SQLOLEDB Returns No Data When Using AutoFetch Option with Fast Forward Cursors
(303446) - The SQL Server native provider (SQLOLEDB) may return no data for a VARCHAR field that is larger than 255 characters under the following conditions: The properties for the rowset will create a Fast Forward cursor. The AutoFetch property (a... 97) 2/8/2012 293659 BUG: SQL Server ODBC Driver Incorrectly Maps Unicode Datatypes with SQL_C_DEFAULT
(293659) - Client applications that call the ODBC API SQLBindCol() function to bind a Unicode data column using SQL_C_DEFAULT will be bound as SQL_C_CHAR. When you call SQLDescribeCol() on a Unicode datatype, the column's datatype will be reported as SQL_WCHAR,... 98) 2/4/2012 294160 BUG: Update of Newly Inserted Row Causes DB_E_ERRORSOCCURRED
(294160) - On updating a row which has been newly inserted into a table, whether through an OLEDB rowset or an ActiveX Data Objects (ADO) recordset, the following error may occur: (0x80040e21, DB_E_ERRORSOCCURRED) Multiple-step OLE DB operation generated errors.... 99) 2/2/2012 294149 BUG: Function Sequence Error Not Returned for Transactions When Connection Pooling Is Disabled
(294149) - When ODBC connection pooling is disabled, using the following sequence in a loop does not result in a "Function sequence error": SQLExecDirect SQLFetch SQLSetStmtOption (SQL_ATTR_AUTOCOMMIT,SQL_AUTOCOMMIT_OFF) SQLTransact(SQL_COMMIT) SQLSetStmtOption... 100) 2/7/2012 294140 FIX: Connection Pooling Causes Windows 2000 Computer with MDAC 25/2.5 SP1 to Stop Responding
(294140) - When an application that uses multiple threads that share a global environment handle implements Open Database Connectivity (ODBC) connection pooling, the application may stop responding (hang) on the platforms listed above with MDAC version 2.5 or... 101) 2/4/2012 286370 PRB: OpenQuery Function Fails with Queries That Exceed 8000 Characters
(286370) - When you try to execute an extremely long query text (greater than 8000 characters) inside of an OPENQUERY function, with a linked server, you may see error messages similar to: Server: Msg 170, Level 15, State 1, Line 1 Line 1: Incorrect syntax near... 102) 2/6/2012 281646 FIX: Buffer Overrun When Using SQLConnectW with ODBC Pooling
(281646) - When you call the ODBC function SQLConnectW and supply non-null terminated strings for the data source name (DSN), user ID (UID), or password (PWD) parameters along with length indicators indicating the exact byte length of the strings, this may later... 103) 2/7/2012 281633 FIX: SQLOLEDB Provider Incorrectly Leaves Transaction Open
(281633) - Running a certain sequence of commands involving explicit transactions and parameters in an application program using the SQLOLEDB Provider incorrectly leaves an uncommitted transaction open. This can cause severe blocking and other problems. 104) 2/9/2012 280084 PRB: Parameters.Refresh Fails Using Parameter Token in Nested SQL
(280084) - When you call the ActiveX Data Objects (ADO) Parameters.Refresh function on a SQL statement that contains parameter tokens inside of a nested SELECT statement, the following error may be reported by the SQL Server OLEDB Provider and SQL Server ODBC... 105) 2/9/2012 265885 FIX: Cannot Get OLE DB Errors on Japanese Windows 95 and Windows 98
(265885) - When you run an OLE DB or ActiveX Data Objects (ADO) application on Japanese Windows 95 or Japanese Windows 98 with MDAC 2.5 installed, Japanese error messages that are raised by the OLE DB Core Services layer are blank. When an error in the OLE DB...
1
.... 3
4
5
6
[ 7 ]
8
9
10
11
.... .... 74
75
Previous Page
Page 7 of 75
Next Page
|