ADO, DAO and RDO in Visual Basic

Results 1 to 3 of 3

Thread: ADO, DAO and RDO in Visual Basic

  1. #1
    Join Date
    Dec 1969

    Default ADO, DAO and RDO in Visual Basic

    Can someone explain to me the major differences between AD0, DAO and RDO ~ and what considerations to keep in mind when choosing one of these?<BR>Thanks!

  2. #2
    John Kim Guest

    Default Same and different

    All are data access method.<BR>So you have to contact one of them when you see DB.<BR>Unlike DAO and RDO, ADO is more independent in hierarchy and more powerful to make connection with OLE db.<BR>and so on...

  3. #3
    Steve M Guest

    Default RE: ADO, DAO and RDO in Visual Basic

    In historical order:<BR><BR>DAO - Microsoft&#039s first data access object, geared toward Access but you could use an ODBC DSN. Slowest of the 3. But there are still some VB controls that can only bind to this variety, from the client-server era.<BR><BR>RDO - 2nd generation meant to offer faster access to remote databases (hence the &#039R&#039). Really aimed at SQL Server, but you could use an ODBC DSN for others. Not recommended for MS Access through ODBC.<BR><BR>ADO - Currenly state of the art for both local and remote databases. Can handle ODBC DSNs and direct connection strings with a cleaner, more consistent API. Also rumored to have connection pooling support, but that&#039s really at the ODBC level.<BR>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts