DAO or ADO ?

[Rob Hofkens]

Hello everyone

I am using a SQLServer 2000 as backend and Access 2003 as frontend using a
lot of VB code.
The tables are linked through a DSN less connection.
Since I am still a begining user of Access I am still not sure when to use
DAO or ADO.
I have been doing some code in both and notice some significant differences
how to accomplish something.
I have read about it and came to the conclusion that ADO is going to be the
new standard and wonder if I should go for ADO all the way when I need to
use one of the two ?

Some good advice would be much appriciated !

Rob.

 

[Douglas J. Steele]

Well, I wouldn't assume that "ADO is going to be the new standard", since
it's already been replaced by ADO.Net, which has little resemblance other
than the first 3 letters, but...

It really depends on how you're interacting with SQL Server, but I usually
go with ADO against SQL Server and DAO against Jet (even when building in
Access 97). There's no problem mixing the two in a single application as
long as you're careful to disambiguate.

 

[Rob Hofkens]

Thank you for your advice !

Rob.

Well, I wouldn't assume that "ADO is going to be the new standard", since
it's already been replaced by ADO.Net, which has little resemblance other
than the first 3 letters, but...

It really depends on how you're interacting with SQL Server, but I usually
go with ADO against SQL Server and DAO against Jet (even when building in
Access 97). There's no problem mixing the two in a single application as
long as you're careful to disambiguate.

 

[Rob Hofkens]

I don't know anything of ADO.Net but what I was afraid of was the support of
DAO in future releases of Access.
When my boss one day decides to upgrade MS Office, the last thing I want to
do is to rewrite the code I am creating now.

Rob.