General discussion

Locked

Differences

By isvanand ·
What is the Difference between DAO (Data Access Objects), RDO (Remote Data Objects and ADO's (Activex Data Objects).

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Differences

by Ann777 In reply to Differences

DAO (Data Access Objects) is an application program interface (API) available with Microsoft's Visual Basic that lets a programmer request access to a Microsoft Access database. DAO was Microsoft's first object-oriented interface with databases. DAO objects encapsulate Access's Jet functions. Through Jet functions, it can also access other Structured Query Language (SQL) databases.
To conform with Microsoft's vision of a Universal Data Access (UDA) model, programmers are being encouraged to move from DAO , although still widely used, to ActiveX Data Objects (ADO) and its low-level interface with databases, OLE DB. ADO and OLE DB offer a faster interface that is also easier to program.

Collapse -

Differences

by isvanand In reply to Differences

The question was auto-closed by TechRepublic

Collapse -

Differences

by C1980 In reply to Differences

Try setting a module level boolean, bDoNotUpdate, to True until you are ready to update the bound control, or when it gets focus, and then set it to false. In the Before_Update event, check if it is true, and if so then set the events Cancel to trueand exit the sub.

Collapse -

Differences

by C1980 In reply to Differences

SORRY!
This was a answer to another question and I was too fast in copying.

I wanted to expand on Answer #1 above:

RDO is similar to DAO except it is used to access remote databases. It has less overhead and and creates less network trafficand uses less local resources - So they say...

I find DAO is the best select when accessing large local ACCESS databases, and one could say it was designed with MDBs prefered.

If you are accessing several types of databases or the DBs are remote and you want to be ready for the future, then maybe ADO is the way to go. It was designed user friendly, more efficient, uses less overhead and network traffic and can access more types of DBs than RDO and DAO, so they say.

I would go with the model that best describes your current need if programming in VB, stay away from bound controls under DAO, (except for the using the datacontrol for DBGrids), and use data enviroment classes to respond to all your data access properties and methods. This way you can create different classes for different data access models and easily change in the future.

Then it isn't nessesarily a question of what model is best for the future, but what is best for right now and with little work, can scale to you changing needs.

Collapse -

Differences

by isvanand In reply to Differences

The question was auto-closed by TechRepublic

Collapse -

Differences

by isvanand In reply to Differences

This question was auto closed due to inactivity

Back to Web Development Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums