DevGuru ADO Quick Reference

Microsoft introduced ADO to the world during the winter of 1996. From the inception, ADO was designed to be a high-level interface to provide ease of access to data stored in a wide variety of database sources. The earlier versions of ADO could only access Relational databases with fixed columns and data types. However, since the release of version 2.5, ADO is now able to interface not only with relational databases, but also with non-relational databases, Folders, data files, and even e-mail messages. For example, ADO can now handle data that are contained in a tree-like structure with a root, nodes, and leaves. It can also handle data where the number of columns and the data type vary from row to row. This represents a significant improvement in the usefulness and value of ADO. The recent release of ADO 2.6 (and now 2.7) has extended this scope even farther to support the use of XML in conjunction with SQL Server 2000. This added capability allows the Stream object to contain not only an XML command that can then be executed against SQL Server 2000, but also XML data returned as a result of a query. This latest release also offers improved performance of commands that only return a single row and more detailed information to help with errors. In ADO 2.6 and greater, the Command object has gained three new properties, CommandStream, Dialect, and NamedParameters. The Parameter and Record objects both now support a Properties Collection. Also note that the Status property is now filled with information to help with the `Errors Occurred` error. Check It Out. The key to this newly-found versatility is the component-based technology of OLE DB. OLE DB was conceived by Microsoft as an answer to the expanding needs of the Internet and e-commerce. Microsoft has an ultimate goal of universal data access and OLE DB represents an important evolutionary step towards reaching that goal.