This document provides late-breaking or other information that supplements the Microsoft ActiveX Data Objects version 1.5 documentation.
--------
CONTENTS
--------
1. PRODUCT DESCRIPTION
2. NEW FEATURES
3. INSTALLATION NOTES
3.1 Before You Run Setup
3.1.1 Hardware Requirements
3.1.2 Software Requirements
4. TECHNICAL SUPPORT
4.1 Visiting the Microsoft ActiveX Data Objects Web Site
4.2 Joining the OLE DB Public Newsgroup For Discussion of ADO
5. KNOWN ISSUES
----------------------
1. PRODUCT DESCRIPTION
----------------------
ActiveX Data Objects is an Automation based interface for accessing data. ActiveX Data Objects (ADO) uses the OLE DB interface to access a broad range of data sources, including but not limited to data provided via ODBC.
Users of RDO and DAO should quickly become comfortable with programming to ADO, the overall design of ADO comes from our experience in developing those interfaces.
--------------------------
2. NEW FEATURES IN ADO 1.5
--------------------------
This release of ADO adds several exciting features to give the developer more power and control in their applications. (See the documentation for more information about using these features). New features include:
* Integration with the Microsoft Client Cursors
As in RDO 2.0, developers now have a high performance client-side cursor engine which supports optimistic batch updating, disconnected Recordset objects, and more.
* Commands as Connection Methods
Using this feature, Commands associated with a connection become methods on that connection interface.
* Data Remoting
Using this feature, ADO users can transmit data across HTTP to a client, work on that data, and submit it back to the HTTP server again.
---------------------
3. INSTALLATION NOTES
---------------------
3.1 Before You Run Setup
Before you install Microsoft ActiveX Data Objects, make sure that your client and server computers meet the minimum hardware and software requirements.
3.1.1 Hardware Requirements
To install ActiveX Data Objects, you must meet certain hardware requirements, which include:
╖ Any Windows 95 or Windows NT x86-compatible computer, or Digital Equipment Corporation ALPHA processor-based computer.
╖ A hard disk with a minimum of 14 megabytes (MB) available space for a full installation of all the updated components required for ADO to run.
╖ A minimum of 12 MB of RAM for client computers.
╖ A minimum of 24 MB of RAM for server computers (32 MB of RAM recommended).
3.1.2 Software Requirements
Before you install ADO, your computer must meet the following software requirements:
╖ Any of the following platforms: Windows 95, Windows NT Workstation 4.0 or later, or Windows NT Server 4.0 (with Service Pack 3) or later.
To use ADO you will need programming environment which supports Automation objects. Currently this includes (but is not limited to) products such as Microsoft IIS 3.0 or 4.0 (with Active Server Pages), the products in Microsoft Office and Microsoft Visual Studio.
--------------------
4. TECHNICAL SUPPORT
--------------------
4.1 Visiting the Microsoft ActiveX Data Objects Web Site
You can visit the Microsoft ActiveX Data Objects Home Page on the World Wide Web for documentation updates and information about other related technologies. The address is http://www.microsoft.com/data/ado/.
4.2 Joining the OLE DB Public Newsgroup for discussion of ActiveX Data Objects
To facilitate discussion, information sharing, and tips trading, Microsoft has set up a public newsgroup: microsoft.public.oledb. You are welcome to post articles and messages to this unmoderated, unsupported newsgroup. Microsoft does not guarantee responses or direct support. For more information, visit the Microsoft OLE DB Web site, http://www.microsoft.com/data/oledb/.
---------------
5. KNOWN ISSUES
---------------
╖ When using the ADO Connection object's Open method in Microsoft Visual C++ or Microsoft Visual J++, or other languages which require all optional parameters to be specified, you need to specify a fourth parameter of -1. This parameter is a placeholder for a future option. Microsoft Visual Basic users don't need to set this parameter, as it will default to the correct value.
╖ If you are doing a join query against Oracle, and ask for a Keyset or Dynamic cursor, you'll get an error rather than a downgraded the cursor. Oracle supports only Static read only cursors with joins.
╖ Executing two or more Command objects on the same connection to a Microsoft SQL Server database will cause an error if any of the Command objects is a stored procedure with output parameters. If you're executing Microsoft SQL Server stored procedures with output parameters, you must use separate connections for each such Command object, or else disconnect the other Command objects from the connection (for example, in Microsoft Visual Basic, Set cmd.ActiveConnection = Nothing)
╖ When using an ORDER BY clause in a query against Microsoft SQL server with Microsoft SQL Server Sevice Pack 3 installed, columns referenced in the ORDER BY clause must also be referenced in the SELECT clause.
╖ When opening a Recordset with the CursorLocation property set to adUseClient (that is, a client-side cursor), the UnderlyingValue property is not available on Field objects of the resulting Recordset.
╖ In ADO 1.5, it's possible to copy values from one recordset field to another by using a command line such as:
It has been found that explictly specifying .Value on both sides of the expression will improve performance and will avoid a known issue with a small memory leak in this area. The new syntax to use would be:
