MDAC (ADO, OLEDB, ODBC) Knowledge Base Articles
Back to the list.
MDAC (ADO, OLEDB, ODBC) KB Article(s)   99">MDAC (ADO, OLEDB, ODBC)?

1  2  3  4  [ 5 ]  6  7  8  9  .... ....  80  81 
Previous Page    Page 5 of 81    Next Page



There are 1213 KB Article(s).

61) 2/11/2004 258242258242  258242.html">Memory allocation for the IRowset object in SQLOLEDB provider
(258242) - This article describes how the Microsoft OLE DB provider for SQL Server (SQLOLEDB) that is included with Microsoft Data Access Components (MDAC), allocates memory for the IRowset object. The article also discusses the differences in the memory...

62) 2/4/2004 833388833388  833388.html">You cannot create out-of-process providers with MDAC OLE DB components
(833388) - You cannot create out-of-process providers with Microsoft Data Access (MDAC) OLE DB components.

63) 1/31/2004 138809138809  138809.html">PRB: Update Conflict w/Remote View When WhereType Set to Time
(138809) - Calling TABLEUPDATE() on a SQL table does not succeed in the following situation. A remote view on a SQL table contains a timestamp field, and the WhereType property of the view is set to "Key & Timestamp." When updates are sent to the remote SQL...

64) 1/15/2004 832483832483  832483.html">MS04-003: Buffer overrun in an MDAC function could allow code execution
(832483) - Microsoft has released security bulletin MS04-003. The security bulletin contains all the relevant information about the security patch, including file manifest information and deployment options. To view the complete security bulletin, visit the...

65) 1/14/2004 297980297980  297980.html">HOWTO: Use ADOX to Create an AutoNumber Field of Replication ID Field Size
(297980) - You can use the Microsoft Access user interface to create an AutoNumber field, in which the field size can be Long Integer or Replication ID. If you select Replication ID as the field size, a globally unique identifier (GUID) is automatically...

66) 1/6/2004 818519818519  818519.html">FIX: Cannot connect to named instance of SQL Server when a fully qualified domain name is specified
(818519) - When you try to establish a connection to a named instance of Microsoft SQL Server in another domain, if an instance of SQL Server with the same named instance (and the same SQL Server name) exists in the local domain, you are connected to the...

67) 12/14/2003 824304824304  824304.html">The Depth property of the Level object always returns -1
(824304) - The Depth property of an instance of the Level object always returns -1 instead of the actual depth level.

68) 12/14/2003 817845817845  817845.html">FIX: "Login Failed for User 'SYSTEM'" Error When You Use OPENROWSET Function Without UserName
(817845) - When you run a query with the OPENROWSET function, and you do not specify the username and password in the function, you receive the following error message: Login failed for user 'SYSTEM'

69) 12/14/2003 811347811347  811347.html">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...

70) 12/14/2003 314639314639  314639.html">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.

71) 12/14/2003 314635314635  314635.html">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...

72) 12/14/2003 312495312495  312495.html">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...

73) 12/14/2003 308262308262  308262.html">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.

74) 12/14/2003 303446303446  303446.html">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...

75) 12/14/2003 293659293659  293659.html">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,...


1  2  3  4  [ 5 ]  6  7  8  9  .... ....  80  81 
Previous Page    Page 5 of 81    Next Page