DAO or ADO?

[Mark O'Brien]

Out of interest, which do most people prefer to usewhen messing around with VBA in Access? ADO or DAO?

Are there some things that are easier with ADO or vice versa?

I'm beginning to see some things in Excel VBA that are easier with obsolete objects rather than their replacements. However, since my DB is going to last 20 years...oh hold one.... ...I'd like to think that my DB will still work if I choose ADO over DAO.

 

[NateO]

However, since my DB is going to last 20 years...oh hold one.... ...I'd like to think that my DB will still work if I choose ADO over DAO.

Don't bet your house on it, once Vb .Net is standard in Access you'll certainly need to change/convert your code. How do feel about Access now?

I personally think DAO is more straight-forward, but Microsoft must've found it to be less robust than the ActiveX Data Object model, otherwise they probably would have ramped DAO up, versus trashing it. Be careful when you write your code, i.e., don't just pull the wisenheimer:

dim rs as recordset

Specifically declare whether it's ado or dao, e.g.,

dim rs as ADODB.recordset

Otherwise, you're actually rolling the dice regarding the placement (priority) of library references, unless you specifically know. Good habbit though, won't hurt ya.

Are you sure your data's normalized?