406) 6/8/2006 Q216519 PRB: SQL Server 6.0 Does Not Work with SQLOLEDB Provider in a SQL Server 7.0 Distributed Query (Q216519)
The SQLOLEDB provider returns the following error message when accessing a SQL Server 6.0 in a SQL Server 7.0 distributed query: 407) 9/6/2007 Q216822 PRB: Index Server: "ADO Could Not Find the Specified Provider" (Q216822)
When you use ActiveX Data Objects (ADO) in a Visual Basic application to query an Index Server, you may receive the following error message: 408) 8/20/2007 Q221552 PRB: SQL Distributed Query with Oracle NUMERIC Column Gives Error (Q221552)
Attempting to use an Oracle linked server using the MSDAORA OLE DB provider, which queries a table with a NUMERIC column, may give an error similar to the following: 409) 6/7/2007 Q220915 PRB: SQL Distributed Query with Oracle Needs Oracle Client and Networking Components (Q220915)
Attempting to use a SQL 7.0 linked server using the Microsoft OLE DB Provider for Oracle, may result in the following error message: 410) 9/26/2007 Q222937 INF: Creating a Linked Server to DB2 using Microsoft OLE DB Provider for DB2 (Q222937)
This article provides a sample SQL script for creating a linked server to DB2 using sp_addlinkedserver, and issues a few queries to illustrate the Distributed Query Processing (DQP) using DB2OLEDB, the Microsoft OLE DB provider for DB2. Ple 411) 8/15/2006 Q225047 FIX: Java OLE DB Simple Provider Does Not Work Reliably (Q225047)
An OLE DB Provider created using the Visual J++ 6.0 and the OLE DB Simple Provider Toolkit does not work reliably. When attempting to use such a provider from ActiveX Data Object (ADO) via the Recordset.Open() method, the following error oc 412) 8/16/2007 Q229741 BUG: Connection Failure with ADO 2.1 and the Jet 3.51 Provider (Q229741)
If you try to set read, write, or read/write access permissions using the 413) 8/11/2006 Q229757 FIX: Oracle OLEDB Provider Returns Err: "ORA06502: PL/SQL..." (Q229757)
When using the Microsoft Oracle OLEDB provider it is possible that you may receive the following error message: 414) 9/11/2006 Q228935 FIX: Uninitialized String Variables, Empty String Values, Jet Provider, and Errors Occurred (Q228935)
If a WITH statement is used to store an empty string value to one field and an uninitialized string to the very next field, an error will occur when using the Microsoft OLE DB Provider for Jet 3.51 or 4.00 that shipped with MDAC versions pr 415) 2/2/2006 Q229919 HOWTO: Retrieve a Recordset from an Oracle Stored Procedure Using ADO on ASP (Q229919)
This article demonstrates how to call an Oracle package to retrieve a recordset using ADO on Active Server Pages (ASP). 416) 9/29/2007 Q229929 INFO: Registry Entries and Keywords for SQL Server Connection Strings (Q229929)
This article describes the different registry entries that are created when you create a data source name (DSN) by using the Microsoft SQL Server ODBC Driver. 417) 9/29/2007 Q230152 PRB: Cannot Add Rows to a Replica Database with ADO (Q230152)
When you try to insert a row into an Access 97 Design Master or Replica database with either the Microsoft Access ODBC Driver or the Microsoft OLE DB Provider for Jet that ships with MDAC 2.1 GA, the following error occurs: 418) 9/5/2007 Q230496 HOWTO: Compacting Microsoft Access Database Through OLE DB (Q230496)
OLE DB specification doesn't provide interfaces to compact or repair databases. However, the OLE DB Provider for Microsoft Jet version 4.0 exposes this functionality through a custom interface: IJetCompact (TDataSource cotype). IJetCompact 419) 7/25/2007 Q230501 HOWTO: Compact Microsoft Access Database via ADO (Q230501)
Although ADO specification does not provide objects to compact or repair Microsoft Access databases, this capability can be achieved by using the ADO extension: Microsoft Jet OLE DB Provider and Replication Objects (JRO). This capability wa 420) 8/19/2007 Q232144 INFO: Jet OLE DB Provider Version 4.0 Supports SELECT @@Identity (Q232144)
The Jet OLE DB version 4.0 provider supports the SELECT @@Identity query that allows you to retrieve the value of the auto-increment field generated on your connection. Auto-increment values used on other connections to your database do not
1
2
.... .... 24
25
26
27
[ 28 ]
29
30
31
32
.... 35
Previous Page
Page 28 of 35
Next Page
|