Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


Tip of the Day
Language: Enterprise
Expertise: All
Mar 21, 2000

Choose Between RDO and DAO Depending Upon the Data Back End You Want

RDO is an object interface that is closely tied to ODBC and is optimized for accessing SQL Server databases, especially from Visual Basic programs. It has little performance overhead on top of ODBC and has a relatively small memory footprint.

On the other hand, the DAO interface is closely tied to and optimized for the Jet local database, which ships in Visual Basic and Microsoft Access. However, for applications that access only SQL Server data, DAO offers less functionality and has a larger memory footprint. In such cases, it is not the recommended interface.

Remember that ADO has now become a widely used superset of most of the unique functionality and supported data sources of both of these interfaces.

Jai Bardhan
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date