ADO: Difference between revisions

From AutoIt Wiki
Jump to navigation Jump to search
(Created page with "{{WIP}}Microsoft's '''ActiveX Data Objects''' ([http://en.wikipedia.org/wiki/ActiveX_Data_Objects ADO]) is a set of [http://en.wikipedia.org/wiki/Component_Object_Model Compon...")
 
m (→‎External links: www.devguru.com: ADO Quick Reference)
 
(127 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{WIP}}Microsoft's '''ActiveX Data Objects''' ([http://en.wikipedia.org/wiki/ActiveX_Data_Objects ADO]) is a set of [http://en.wikipedia.org/wiki/Component_Object_Model Component Object Model] (COM) objects for accessing data sources. A part of MDAC, it provides a middleware layer between programming languages and OLE DB (a means of accessing data stores, whether they be databases or otherwise, in a uniform manner). ADO allows a software developer to write programs that access data without knowing how the database is implemented; developers must be aware of the database for connection only. No knowledge of SQL is required to access a database when using ADO, although one can use ADO to execute SQL commands directly. The disadvantage of the latter is that it introduces a dependency upon the type of database used.
Most of the following text was taken from [http://en.wikipedia.org/wiki/ActiveX_Data_Objects Wikipedia] and [http://www.connectionstrings.com connectionstrings.com]:


ADO is positioned as a successor to Microsoft's earlier object layers for accessing data sources, including Remote Data Objects (RDO) and Data Access Objects (DAO). ADO was introduced by Microsoft in October 1996.
Microsoft's '''ActiveX Data Objects''' (ADO) is a set of [http://en.wikipedia.org/wiki/Component_Object_Model Component Object Model] (COM) objects for accessing data sources. As part of MDAC, it provides a middleware layer between programming languages and OLE DB (a means of accessing data stores, whether they be databases or otherwise, in a uniform manner). ADO allows a software developer to write programs that access data without knowing how the database is implemented; developers must be aware of the database for connection only. No knowledge of SQL is required to access a database when using ADO, although one can use ADO to execute SQL commands directly. The disadvantage of the latter is that it introduces a dependency upon the type of database used.
 
ADO is positioned as a successor to Microsoft's earlier object layers for accessing data sources, including Remote Data Objects (RDO) and Data Access Objects (DAO). ADO was introduced by Microsoft in October 1996.<br />
<br />
 
There are many ways to retrieve, add and change data using ADO. This tutorial only describes a fraction of what can be done with ADO:
* How to read data
* How to use the OLEDB provider, ODBC and other providers are not part of this tutorial
* To open the connection a connection string is used. Setting the properties of the connection object to describe the connection is not part of this tutorial
* The command to retrieve data is specified with the Open method for the RecordSet object. The Command object is not part of this tutorial<br />
<br />
 
Microsoft '''ActiveX Data Objects Extensions for Data Definition Language and Security''' (ADOX) is an extension to the ADO objects and programming model. ADOX includes objects for schema creation and modification, as well as security. Because it is an object-based approach to schema manipulation, you can write code that will work against various data sources regardless of differences in their native syntaxes.<br />
ADOX is a companion library to the core ADO objects. It exposes additional objects for creating, modifying, and deleting schema objects, such as tables and procedures. It also includes security objects to maintain users and groups and to grant and revoke permissions on objects.<br />
''ADOX is not part of this tutorial!''<br />
<br />
 
== How does ADO, OLEDB and ODBC fit together? ==
This chart shows the "big picture" so you can see how this all fits together (Picture taken from http://community.qlik.com/thread/106540).<br />
[[File:db-full-diagram.png|600px|How does ADO, OLEDB and ODBC fit together?]]
 
=== ADO ===
ADO (ADODB) is a generic (COM) database library, that can be used by programming languages to access any type of database for which an OLEDB Provider has been developed.<br />
In this context, ADO is an OLEDB ''Consumer''. It communicates with the OLEDB Provider, which in turn communicates with the database directly or a database server.<br />
For example, to open an Access database, the Connection object of ADODB would specify the Jet OLEDB Provider in its connection string to open and subsequently communicate with the database.<br />
There is also an OLEDB driver that can wrap any ODBC driver. Thus ADO can also talk to any database that exposes an ODBC driver.
 
=== OLEDB ===
OLEDB is a Microsoft standard that defines a set of API (Application Interface) functions for accessing all kind of databases (oracle, db2, MS-based databases etc.).<br />
It is a COM (Component Object Model) API that was a follow-up to the ODBC API.<br />
Typically OLEDB is used to create a database specific driver, known as a ''provider'', that can be implemented by a higher level data access library such as ADO.<br />
 
=== ODBC ===
ODBC is a standard API for accessing SQL based database management systems (DBMS). The designers of ODBC aimed to make it independent of database systems and operating systems.<br />
This is accomplished by using an ODBC driver as a translation layer between the application and the DBMS. The application uses ODBC functions through an ODBC driver manager with which it is linked, and the driver passes the query to the DBMS.<br />
There are commercial products available to access Applications and WebAPIs like Google Sheets, Microsoft SharePoint, Twitter and so on.


== Internals ==
== Internals ==
ADO is made up of four collections and twelve objects. For details please see page → [[ADO Internals]].
== Usage ==
Some basic steps are required in order to be able to access and manipulate data using ADO:
#Create a connection object to connect to the database
#Create a recordset object in order to receive data in
#Open the connection
#Populate the recordset
#Do all the desired searching/processing on the fetched data
#Close the recordset
#Close the connection


ADO is made up of four collections and twelve objects.
=== Create a connection object ===
In AutoIt this is simply done by:
<syntaxhighlight lang="autoit">
Global $oConnection = ObjCreate("ADODB.Connection")
</syntaxhighlight>


==ADO collections==
=== Create a recordset object ===
In AutoIt this is simply done by:
<syntaxhighlight lang="autoit">
Global $oRecordSet = ObjCreate("ADODB.Recordset")
</syntaxhighlight>


; Fields
=== Open the connection ===
[[File:ADO.gif|framed|right|Application-ADO-Provider-Database]]To open the connection you have to build a connection string.
When your application connects to a database or a data file you let ADO utilize a provider to do the job for you. The connection string contains the information that the provider needs to know to be able to establish a connection to the database or the data file.
Because there are different providers and each provider has multiple ways to make a connection there are many different ways to write a connection string. It's like the address when sending a regular mail. Depending on the origin and destination and who is going to make the transport you need to write down the address in different ways.


: This collection contains a set of Field objects. The Collection can be used in either a Recordset object or in a Record object. In a Recordset object, each of the Field objects that make up the Fields collection corresponds to a column in that Record set object. In a Record object, a Field can be an absolute or relative URL that points into a tree-structured [[Namespace (computer science)|namespace]] (used for [[semi-structured data]] providers like the Microsoft OLE DB Provider for Internet Publishing) or as a reference to the default Stream object associated with that Record object.
==== Connection string ====
; Properties
The connection string is really just a string inside the application you pass on to the connection object. The property is passed through the Open function of the connection object.


: An object can have more than one Property object, which are contained in the object's Properties collection.
For details please see page → [[ADO ConnectionString]].
; Parameters


: A Command object can have several Parameter commands to change its predefined behaviour, and each of the Parameter objects are contained in the Command object's Parameters collection
==== Connection properties ====
; Errors
For details please see [https://msdn.microsoft.com/en-us/library/windows/desktop/ms681546%28v=vs.85%29.aspx Connection Object Properties, Methods, and Events].


: All provider-created errors are passed to a collection of Error objects, while the Errors collection itself is contained in a Connection object. When an ADO operation creates an error, the collection is cleared and a new group of Error objects is created in the collection.
=== Populate the recordset ===
The ADO Recordset object is used to contain the set of data extracted from a database or file and is composed of records (rows) and fields (columns).<br />


==ADO objects==
The Recordset object is the heart of ADO. Via this object, we can select desired data. Equally important is the ability to move around inside the database. However, the functionality of the provider may impose limitations.<br />


; Connection
RecordSet.Open(Source, Connection, CursorType, LockType, Options)
: The connection object is ADO's connection to a data store via OLE DB. The connection object stores information about the session and provides methods of connecting to the data store. As some data stores have different methods of establishing a connection, some methods may not be supported in the connection object for particular OLE DB providers. A connection object connects to the data store using its 'Open' method with a connection string which specifies the connection as a list of key value pairs (for example: "Provider='SQLOLEDB';Data Source='TheSqlServer'; Initial Catalog='Northwind';Integrated Security='SSPI';"). The start of which must identify the type of data store connection that the connection object requires:
:* an OLE DB provider (for example SQLOLEDB), using the syntax "provider=";
:* a file name, using the syntax "file name=";
:* a remote provider and server (see RDS), using the syntax "Remote provider=" and "Remote server="; or
:* an absolute URL, using the syntax "URL="
; Command
: After the connection object establishes a session to the data source, instructions are sent to the data provider via the command object. The command object can send SQL queries directly to the provider through the use of the CommandText property, send a parameterised query or stored procedure through the use of a Parameter object or Parameters collection or run a query and return the results to a dataset object via the Execute method. There are several other methods that can be used in the Command object relating to other objects, such as the Stream, RecordSet or Connection objects.
; Recordset
: A recordset is a group of records, and can either come from a base table or as the result of a query to the table. The RecordSet object contains a Fields collection and a Properties collection. The Fields collection is a set of Field objects, which are the corresponding columns in the table. The Properties collection is a set of Property objects, which defines a particular functionality of an OLE DB provider. The RecordSet has numerous methods and properties for examining the data that exists within it. Records can be updated in the recordset by changing the values in the record and then calling on the Update or UpdateBatch method.
; Immediate
: The recordset is locked using the adLockOptimistic or adLockPessimistic lock. The data are updated at the data source after the record is changed and the Update method is called.
; Batch
: The recordset is locked using adLockBatchOptimistic and each time Update is called the data are updated in a temporary buffer. Finally, when UpdateBatch is called the data are completely updated back at the data source. This has the advantage of it all being done in memory, and if a problem occurs then UpdateCancel is called and the updates are not sent to the data source
; Transaction
: If the OLE DB provider allows it, transactions can be used. To start the transaction, the programmer invokes the BeginTrans method and does the required updates. When they are all done, the programmer invokes the CommitTrans method. RollbackTrans can be invoked to cancel any changes made inside the transaction and rollback the database to the state before the transaction began
; Record
: This object represents one record in the database and contains a fields collection. A RecordSet consists of a collection of Record objects.
; Stream
: A stream, mainly used in a RecordSet object, is a means of reading and writing a stream of bytes. It is mostly used to save a recordset in an XML format, to send commands to an OLE DB provider as an alternative to the CommandText object and to contain the contents of a binary or text file.
; Parameter
: A parameter is a means of altering the behaviour of a common piece of functionality, for instance a stored procedure might have different parameters passed to it depending on what needs to be done; these are called parameterised commands.
; Field
: Each Record object contains many fields, and a RecordSet object has a corresponding Field object also. The RecordSet object's Field object corresponds to a column in the database table that it references.
; Property
: This object is specific to the OLE DB provider and defines an ability that the provider has implemented. A property object can be either a built-in property — it is a well-defined property implemented by ADO already and thus cannot be altered — or can be a dynamic property — defined by the underlying data provider and can be changed
; Error
: When an OLE DB provider error occurs during the use of ADO, an Error object will be created in the Errors collection. Other errors do not go into an Error object, however. For instance, any errors that occur when manipulating data in a RecordSet or Field object are stored in a Status property.SK


== Basic usage ==
The Open method is called on a Recordset object to open a cursor which gives you access to the records contained in the base table, the results from a query (used in the examples of this tutorial), or a previously saved Recordset.
Some basic steps are required in order to be able to access and manipulate data using ADO :
 
#Create a connection object to connect to the database.
For details please see page → [[ADO RecordSet Populate]].
#Create a recordset object in order to receive data in.
 
#Open the connection
=== Search/process the fetched data===
#Populate the recordset by opening it and passing the desired table name or SQL statement as a parameter to ''open'' function.
ADO provides methods and properties to
#Do all the desired searching/processing on the fetched data.
* move around in the RecordSet
#Commit the changes you made to the data (if any) by using ''Update'' or ''UpdateBatch'' methods.
* search for rows
#Close the recordset
* write the recordset to a 2D array or a single record to a string
#Close the connection
* save the recordset to a file
* sort the records
* delete rows from the RecordSet
and much more.<br />
For details please see page → [[ADO RecordSet Process]].
 
=== Close the recordset===
Close the recordset and assign a new value to the object to release it:
<syntaxhighlight lang="autoit">
$oRecordSet.Close()
$oRecordSet = 0
</syntaxhighlight>
 
=== Close the connection===
Close the connection and assign a new value to the object to release it:
<syntaxhighlight lang="autoit">
$oConnection.Close()
$oConnection = 0
</syntaxhighlight>


=== ASP example ===
=== Handle events ===
To handle events you need to create an event object and set the name of a function which then handles the event:
<syntaxhighlight lang="autoit">
Global $oConnection = ObjCreate("ADODB.Connection")
Global $oConnectionEvent = ObjEvent($oConnection, "oConnection_")


Here is an [[Active Server Pages|ASP]] example using ADO to select the "Name" field, from a table called "Phonebook", where a "PhoneNumber" was equal to "555-5555".  
Func oConnection_ConnectComplete($oError, $iStatus, $oConnection)
    If $iStatus = $iStatusErrorsOccurred Then _
        ConsoleWrite("CONNECTION ERROR: " & $oError.Description)
EndFunc
</syntaxhighlight>
For details please see page → [[ADO Event handling]].


<source lang=asp>
== Examples ==
dim myconnection, myrecordset, name
* [[ADO_Example_DB2|IBM DB2]]
set myconnection = server.createobject("ADODB.Connection")
* [[ADO_Example_Access|Microsoft Access]]
set myrecordset = server.createobject("ADODB.Recordset")
* [[ADO_Example_Excel|Microsoft Excel]]
* [[ADO_Example_Project|Microsoft Project]]
* [[ADO_Example_SQL_Server|Microsoft SQL Server]]
* [[ADO_Example_MySQL|MySQL]]
* [[ADO_Example_Oracle|Oracle Database Server]]
* [[ADO_Example_PostgreSQL|PostgreSQL]]
* [[ADO_Example_SQLite|SQLite]]
* [[ADO_Example_TextFile|Text files]]


myconnection.open mydatasource
== Tools ==
myrecordset.open "Phonebook", myconnection
Some (AutoIt) tools to make life easier can be found on page → [[ADO Tools]].
myrecordset.find "PhoneNumber = '555-5555'"
name = myrecordset.fields.item("Name")
myrecordset.close


set myrecordset = nothing
== UDF ==
set myconnection = nothing
mLipok has written an [https://www.autoitscript.com/wiki/User_Defined_Functions#Databases_and_web_connections UDF] to access all kind of databases using ADO.<br>
</source>


This is equivalent to the following ASP code, which uses plain SQL instead of the functionality of the Recordset object:
water has written an [https://www.autoitscript.com/forum/index.php?showtopic=106163 UDF] to access Microsoft Active Directory using ADO.
<source lang=asp>
dim myconnection, myrecordset, name
set myconnection = server.createobject("ADODB.connection")
myconnection.open mydatasource
set myrecordset = myconnection.execute("SELECT Name FROM Phonebook WHERE PhoneNumber = '555-5555'")
name = myrecordset(0)
</source>


==Software support==
== Internal links ==
ADO is supported in ASP, [[Embarcadero Delphi | Delphi]], [[PowerBuilder]], and in Visual Basic for Applications (VBA).
Links to ADO related threads on the forum:


== See also ==
* [http://www.autoitscript.com/forum/index.php?showtopic=180850 ADO (by mLipok)] - A modifed version of the _sql.au3 UDF to access all kind of databases.
* [[ADO.NET]]
* [http://www.autoitscript.com/forum/topic/169897-activex-data-objects-dsn-less-database-connection-demo/#entry1241099 ActiveX Data Objects (by GreenCan)] - DSN-Less Database connection demo.
* [[Comparison of ADO and ADO.NET]]
* [http://www.autoitscript.com/forum/index.php?showtopic=105875 ADODB (by spudw2k)] - ADODB Example.
* [http://www.autoitscript.com/forum/index.php?showtopic=127101 MS SQL (by TheLuBu)] - MSSQL.au3.
* [http://www.autoitscript.com/forum/index.php?showtopic=51952 MS SQL (by ChrisL)] - _SQL.au3. ADODB Connection.
* [http://www.autoitscript.com/forum/index.php?showtopic=20814 MySQL (by cdkid)] - MySQL relational database management system UDF.
* [https://www.autoitscript.com/forum/topic/122360-mysql-odbc-connector-udf MySQL (by James)] - MySQL ODBC Connector.


==External links==
== External links ==
*[http://msdn2.microsoft.com/en-us/library/ms805098.aspx Microsoft ADO page]
*[http://www.connectionstrings.com/ Database connection strings]
*[http://devguru.com/technologies/ado/index.asp DevGuru ADO Quick Reference]


{{Microsoft APIs}}
*[http://msdn.microsoft.com/en-us/library/windows/desktop/ms675532%28v=vs.85%29.aspx MSDN: Microsoft ADO page]
*[http://msdn.microsoft.com/en-us/library/windows/desktop/ms675944%28v=vs.85%29.aspx MSDN: ADO object model]
*[https://www.devguru.com/content/technologies/ado/home.htmlhome www.devguru.com: ADO Quick Reference]
*[http://www.w3schools.com/asp/ado_intro.asp www.w3schools.com: Learn ADO]
*[https://www.connectionstrings.com/ www.connectionstrings.com: Learn about many different Connection Strings]


{{DEFAULTSORT:Activex Data Objects}}
[[Category:Tutorials]][[Category:ADO]]
[[Category:Microsoft application programming interfaces]]

Latest revision as of 16:28, 6 September 2020

Most of the following text was taken from Wikipedia and connectionstrings.com:

Microsoft's ActiveX Data Objects (ADO) is a set of Component Object Model (COM) objects for accessing data sources. As part of MDAC, it provides a middleware layer between programming languages and OLE DB (a means of accessing data stores, whether they be databases or otherwise, in a uniform manner). ADO allows a software developer to write programs that access data without knowing how the database is implemented; developers must be aware of the database for connection only. No knowledge of SQL is required to access a database when using ADO, although one can use ADO to execute SQL commands directly. The disadvantage of the latter is that it introduces a dependency upon the type of database used.

ADO is positioned as a successor to Microsoft's earlier object layers for accessing data sources, including Remote Data Objects (RDO) and Data Access Objects (DAO). ADO was introduced by Microsoft in October 1996.

There are many ways to retrieve, add and change data using ADO. This tutorial only describes a fraction of what can be done with ADO:

  • How to read data
  • How to use the OLEDB provider, ODBC and other providers are not part of this tutorial
  • To open the connection a connection string is used. Setting the properties of the connection object to describe the connection is not part of this tutorial
  • The command to retrieve data is specified with the Open method for the RecordSet object. The Command object is not part of this tutorial


Microsoft ActiveX Data Objects Extensions for Data Definition Language and Security (ADOX) is an extension to the ADO objects and programming model. ADOX includes objects for schema creation and modification, as well as security. Because it is an object-based approach to schema manipulation, you can write code that will work against various data sources regardless of differences in their native syntaxes.
ADOX is a companion library to the core ADO objects. It exposes additional objects for creating, modifying, and deleting schema objects, such as tables and procedures. It also includes security objects to maintain users and groups and to grant and revoke permissions on objects.
ADOX is not part of this tutorial!

How does ADO, OLEDB and ODBC fit together?

This chart shows the "big picture" so you can see how this all fits together (Picture taken from http://community.qlik.com/thread/106540).
How does ADO, OLEDB and ODBC fit together?

ADO

ADO (ADODB) is a generic (COM) database library, that can be used by programming languages to access any type of database for which an OLEDB Provider has been developed.
In this context, ADO is an OLEDB Consumer. It communicates with the OLEDB Provider, which in turn communicates with the database directly or a database server.
For example, to open an Access database, the Connection object of ADODB would specify the Jet OLEDB Provider in its connection string to open and subsequently communicate with the database.
There is also an OLEDB driver that can wrap any ODBC driver. Thus ADO can also talk to any database that exposes an ODBC driver.

OLEDB

OLEDB is a Microsoft standard that defines a set of API (Application Interface) functions for accessing all kind of databases (oracle, db2, MS-based databases etc.).
It is a COM (Component Object Model) API that was a follow-up to the ODBC API.
Typically OLEDB is used to create a database specific driver, known as a provider, that can be implemented by a higher level data access library such as ADO.

ODBC

ODBC is a standard API for accessing SQL based database management systems (DBMS). The designers of ODBC aimed to make it independent of database systems and operating systems.
This is accomplished by using an ODBC driver as a translation layer between the application and the DBMS. The application uses ODBC functions through an ODBC driver manager with which it is linked, and the driver passes the query to the DBMS.
There are commercial products available to access Applications and WebAPIs like Google Sheets, Microsoft SharePoint, Twitter and so on.

Internals

ADO is made up of four collections and twelve objects. For details please see page → ADO Internals.

Usage

Some basic steps are required in order to be able to access and manipulate data using ADO:

  1. Create a connection object to connect to the database
  2. Create a recordset object in order to receive data in
  3. Open the connection
  4. Populate the recordset
  5. Do all the desired searching/processing on the fetched data
  6. Close the recordset
  7. Close the connection

Create a connection object

In AutoIt this is simply done by: 

Global $oConnection = ObjCreate("ADODB.Connection")

Create a recordset object

In AutoIt this is simply done by: 

Global $oRecordSet = ObjCreate("ADODB.Recordset")

Open the connection

Application-ADO-Provider-Database

To open the connection you have to build a connection string.

When your application connects to a database or a data file you let ADO utilize a provider to do the job for you. The connection string contains the information that the provider needs to know to be able to establish a connection to the database or the data file. Because there are different providers and each provider has multiple ways to make a connection there are many different ways to write a connection string. It's like the address when sending a regular mail. Depending on the origin and destination and who is going to make the transport you need to write down the address in different ways.

Connection string

The connection string is really just a string inside the application you pass on to the connection object. The property is passed through the Open function of the connection object.

For details please see page → ADO ConnectionString.

Connection properties

For details please see Connection Object Properties, Methods, and Events.

Populate the recordset

The ADO Recordset object is used to contain the set of data extracted from a database or file and is composed of records (rows) and fields (columns).

The Recordset object is the heart of ADO. Via this object, we can select desired data. Equally important is the ability to move around inside the database. However, the functionality of the provider may impose limitations.

RecordSet.Open(Source, Connection, CursorType, LockType, Options)

The Open method is called on a Recordset object to open a cursor which gives you access to the records contained in the base table, the results from a query (used in the examples of this tutorial), or a previously saved Recordset.

For details please see page → ADO RecordSet Populate.

Search/process the fetched data

ADO provides methods and properties to

  • move around in the RecordSet
  • search for rows
  • write the recordset to a 2D array or a single record to a string
  • save the recordset to a file
  • sort the records
  • delete rows from the RecordSet

and much more.
For details please see page → ADO RecordSet Process.

Close the recordset

Close the recordset and assign a new value to the object to release it: 

$oRecordSet.Close()
$oRecordSet = 0

Close the connection

Close the connection and assign a new value to the object to release it: 

$oConnection.Close()
$oConnection = 0

Handle events

To handle events you need to create an event object and set the name of a function which then handles the event: 

Global $oConnection = ObjCreate("ADODB.Connection")
Global $oConnectionEvent = ObjEvent($oConnection, "oConnection_")

Func oConnection_ConnectComplete($oError, $iStatus, $oConnection)
    If $iStatus = $iStatusErrorsOccurred Then _
        ConsoleWrite("CONNECTION ERROR: " & $oError.Description)
EndFunc

For details please see page → ADO Event handling.

Examples

Tools

Some (AutoIt) tools to make life easier can be found on page → ADO Tools.

UDF

mLipok has written an UDF to access all kind of databases using ADO.

water has written an UDF to access Microsoft Active Directory using ADO.

Internal links

Links to ADO related threads on the forum:

External links

Retrieved from "https://www.autoitscript.com/w/index.php?title=ADO&oldid=14394"