DAO and Access 2000

[Tony Nichols]

I have a few quick questions regarding DAO and Access
2000.

I am just now beginning to make the conversion to Access
2000 and I have done a lot of DAO programing in Access97.

I am reading things that seem to indicate using DAO beyond
Access97 is not the best practice. I see there is still
DAO reference it is the new version 3.6 in Access 2000.

Should I be learning ADO and converting my DAO code to ADO
as I convert db's to Access 2000 format?

I cannot seem to find any DAO help file information in
Access 2000. Has in been completely removed by Microsoft?

Is there any alternative DAO 3.6 help information?

I have seen some people say you cannot do some things in
ADO that you can in DAO , is this correct?

Thanks in advance for any insights.

Tony Nichols

 

[Ted Allen]

Hi Tony,

I'm sure you will get different opinions on this from
different people, but most of the posts that I have seen
seem to favor sticking with DAO if you will be working
primarily in the Access environment. They claim that DAO
is faster in performing actions within the Access
environment, but that ADO provides more consistency with
programming outside of Access.

If you are familiar with DAO, I would suggest sticking
with it. Of course, you can always use ADO when you need
to, since you can reference both libraries. Just be sure
to explicitly dimension objects that are contained in
both libraries (such as recordsets). This is a good idea
even if you currently only use one library because down
the road you could find the need for the other.

Just my 2 cents. I'll be curious to see other posts as
well.

-Ted Allen

 

[Joe Fallon]

ADO is dead.
Why bother?

Keep using DAO.

Learn VB.Net and ADO.Net now.
The .Net framework is the future.

 

[ALESSANDRO Baraldi]

I have a few quick questions regarding DAO and Access
2000.

I am just now beginning to make the conversion to Access
2000 and I have done a lot of DAO programing in Access97.

I am reading things that seem to indicate using DAO beyond
Access97 is not the best practice. I see there is still
DAO reference it is the new version 3.6 in Access 2000.

Should I be learning ADO and converting my DAO code to ADO
as I convert db's to Access 2000 format?

I cannot seem to find any DAO help file information in
Access 2000. Has in been completely removed by Microsoft?

Is there any alternative DAO 3.6 help information?

I have seen some people say you cannot do some things in
ADO that you can in DAO , is this correct?

Thanks in advance for any insights.

Tony Nichols

If you use JET(BE) is not good idea convert on ADO, because
JET have DAO as Native Library, so you force JET to do double
work....!!!

Different chois if you have MSDE/SQL_SERVER, in this way
you don't need of any background conversion, ADO is designed
and optimized for Server use....!

Sorry for my English....!

Alessandro(IT)