Remote data objects

from Wikipedia, the free encyclopedia

Remote Data Objects (RDO for short) refers to an outdated programming interface from Microsoft on an object-oriented basis for accessing database systems . It was mainly used in Visual Basic applications .

RDO enables developers to directly access data sources on remote computers without having to deal with the complex ODBC interface . RDO provides functions to establish connections to databases, to place queries there and to process the query results. RDO also supports stored procedures and transactions .

Remote Data Objects was included in versions 4, 5, and 6 of Visual Basic. The last version is version 2.0.

Related procedures

RDO was designed by Microsoft to complement the Data Access Objects (DAO) interface . The Access database , which was introduced in the early 1990s, was operated by the Jet Engine . DAO allowed developers to access Jet through program code. The typical elements of relational databases such as tables, columns, relationships between tables and entries could thus be treated as program objects.

However, if it was necessary to access data from existing server databases such as Oracle or DB2 , DAO was subject to restrictions. The ODBC protocol was used for communication with these databases. The data was translated so that the external databases looked like a Jet database to DAO; a complicated and resource-intensive process. In order to be able to address ODBC sources more quickly, the RDO interface was added to DAO.

RDO used a different object model than DAO, so that ODBCDirect was also introduced later , with which developers could access ODBC sources directly via DAO, at a speed comparable to RDO. DAO and RDO were later replaced by ActiveX Data Objects (ADO) and OLE DB ; However, because of the initially reduced functionality and the wide use of DAO, ADO was only able to spread slowly. The current database interface from Microsoft is ADO.NET .

literature

Web links