Remote Data Objects (RDO) is another COM object hierarchy, layered on top of ODBC instead of the Jet engine. When you use DAO to get at an ODBC database, you are actually using RDO objects. RDO is popular among corporate developers because it offers support for features such as prepared statements and calling stored procedures. The most visible manifestation of RDO is the Remote Data Control in Visual Basic, which helped to remedy the truly appalling performance of the Data Control when operating on remote databases. RDO is stable and works well, but is not as popular as DAO. It is unlikely to be developed further.
 The Data Control allows you to build a database form by setting a few properties and linking text boxes to database fields. It queries the database at runtime about the kinds of fields available in the tables to which it’s bound; this works fine with Jet, which has the information readily available, but generates unbelievable traffic over a client/server connection. We’ve watched it by logging ODBC calls, and each data control makes a separate connection; one application might have 10 or 12 database connections open.