1021) 2/10/2002 Q245500Q245500  Q245500.html">PRB: Catastrophic Error Seen with Addition of Datasource Connection to Sybase 11x (Q245500)
When you add an ODBC connection to Sybase 11x and the catalog name is specified in the connection string for the Microsoft OLE DB Provider for ODBC Drivers, this error occurs:

1022) 2/10/2002 Q246262Q246262  Q246262.html">SAMPLE: Sqlfstin: Speed Up OLE DB Inserts By Using IRowsetFastLoad() (Q246262)
The Sqlfstin.exe sample demonstrates how to perform quick, transactional inserts of a large number of records into SQL Server by using the

1023) 2/10/2002 Q251254Q251254  Q251254.html">PRB: "Disk or Network Error" or "Unspecified Error" Returned when Using Jet (Q251254)
When trying to connect to an Access .mdb file, an ODBC error is returned stating "Disk or Network Error". The Microsoft OLE DB Provider for the Microsoft Jet database engine may also return an "Unspecified error" (error code = 0x80004005) m

1024) 2/10/2002 Q250999Q250999  Q250999.html">PRB: RDS Does Not Work Correctly with OLE DB Simple Provider (Q250999)
When the Remote Data Service (RDS) for ActiveX Data Objects (ADO) is used with an OLE DB provider that was built by using the OLE DB Simple Provider (OSP) Toolkit, the following error message may occur:

1025) 2/10/2002 Q258576Q258576  Q258576.html">INFO: Limitations of IRowsetIndex::Seek() Used with Jet database (Q258576)
You can use

1026) 2/10/2002 Q258997Q258997  Q258997.html">INFO: Oracle OLE DB Provider and ROWID Use (Q258997)
Beginning with Microsoft Data Access Components (MDAC) 2.1, the Microsoft OLE DB Provider for Oracle implements the use of ROWIDs for unique row identification. This may generate some unexpected side effects in some circumstances.

1027) 2/10/2002 Q259959Q259959  Q259959.html">INFO: Techniques to Debug Connectivity Issues to an Oracle Server Using the ODBC Driver and OLE DB Provider (Q259959)
Both the Microsoft ODBC for Oracle driver (Msorcl32.dll) and the Microsoft OLE DB Provider for Oracle (Msdaora.dll) use the SQL*Net Client (or Net8 client for Oracle 8x) and the Oracle Call Interface (OCI) library, as well as other Oracle c

1028) 2/10/2002 Q264012Q264012  Q264012.html">PRB: Connectivity Issue with MDAC and Oracle8i (Q264012)
When you attempt to connect to an Oracle 8i database by using the Oracle 8i client and the Microsoft Oracle ODBC Driver (MSORCL32.DLL) version 2.573.4403 (or higher) or the MS Oracle Provider (MSDAORA.DLL) version 2.50.4403.0 (or higher), y

1029) 2/10/2002 Q267550Q267550  Q267550.html">BUG: "Assertion Failed" When You Connect to a SQL Server Through TCP/IP (Q267550)
When you attempt to connect to a SQL Server through TCP/IP on a Windows 98 client, the following error message can occur:

1030) 2/10/2002 Q269344Q269344  Q269344.html">BUG: Microsoft Oracle ODBC Driver and OLE DB Provider Report "Driver Not Capable" (Q269344)
When attempting to enlist in a distributed transaction by using either the Microsoft ODBC for Oracle or the Microsoft OLE DB Provider for Oracle, the following error message occurs:

1031) 2/10/2002 Q271774Q271774  Q271774.html">SAMPLE: How To Manipulate the "Trustee PIN" Jet Property Using ADOX in VC (Q271774)
ADOX.exe demonstrates the use of the

1032) 2/10/2002 Q271908Q271908  Q271908.html">INFO: MDAC Version 2.6 and Later Do Not Contain Jet or Desktop ODBC Drivers (Q271908)
Starting with Microsoft Data Access Components (MDAC) version 2.6, MDAC no longer contains Jet components. In other words, MDAC 2.6 and 2.7 do not include Microsoft Jet, Microsoft Jet OLE DB Provider, and the ODBC Desktop Database Drivers.

1033) 2/10/2002 Q293349Q293349  Q293349.html">PRB: Retrieving Properties with OLE DB May Cause Memory Leak (Q293349)
Whenever an OLE DB consumer application retrieves properties from the provider, it is the responsibility of the consumer application to free the memory associated with the property structures that the provider returns.

1034) 2/10/2002 Q269412Q269412  Q269412.html">FIX: Access Violation Occurs When You Call SQL Server Stored Procedure That Contains PRINT Statement (Q269412)
An access violation occurs when you call a SQL Server stored procedure that contains a PRINT statement that displays a string containing approximately 700 characters.

1035) 2/10/2002 Q279245Q279245  Q279245.html">FIX: Default Column Properties Cleared When You Set or Check Values by Using ADOX to an Access Database (Q279245)
When you set or check the default column values for any column in a table that is contained in an Access 2000 database, the default values for the column are cleared.