ADO versus DAO

[MikeSaunders]

I’m working on a project which needs to read from a dBase format, process some data using an Access 2000 database and then export back to dBase. I’m wondering if anyone has any thoughts on whether to use ADO or DAO. I’ve found DAO to be much more usable with dBase files (you can’t write to a linked DBF with ADO unless you have ADO Service Pack 5 installed, and I haven’t yet found a way to create a dBase file with ADO). However, overall I like ADO better and since it’s newer it would seem in many ways that that’s the way to go.
One option I’ve thought of is using ADO for most things and then DAO for the things that I have to, but from a programmers standpoint it seems a bit hodgepodge to have a mix like that. Any thoughts?

Thanks,

Mike

[LNM]

I would definetely use the DAO to work with Access because it is documented to have the best performance with this db type. As far as dBase - have never used this db.
If DAO is fast with dBase, too, I would use it to communicate with both databases. I think that one of disadvantages of the DAO is the hierarchical structure. Other than that it's pretty flexible.
HTH.

[Iouri]

I would use ADO, because
1. I think it is better
2. ADO is the future and DAO will not be supported soon

Iouri Boutchkine
[email protected]