Access 2003 and DAO

[Dave the Wave]

I just converted an .MDB (Access97) to a Access 2003 MDB file. I got
an error message about DAO no longer being supported by Access 2003.
When I looked at the references listed I noticed newer versions of the
DAO than I was using. Also, everything seems to be working just fine
without any code changes.

Am I missing something?

Thanks for any help!

Dave

 

[(PeteCresswell)]

Per Dave the Wave:

I just converted an .MDB (Access97) to a Access 2003 MDB file. I got
an error message about DAO no longer being supported by Access 2003.
When I looked at the references listed I noticed newer versions of the
DAO than I was using. Also, everything seems to be working just fine
without any code changes.

I've done a few 97=>2003 conversions and don't recall seeing that message.

For me, they've been pretty much transparent DAO-wise.
Mine use DAO 3.6.

On a new front-end .MDB, however, it seems to default to ADO and I need to
explicitly set the ref to DAO.

 

[Dave the Wave]

Per Dave the Wave:

I've done a few 97=>2003 conversions and don't recall seeing that message.

For me, they've been pretty much transparent DAO-wise.
Mine use DAO 3.6.

On a new front-end .MDB, however, it seems to default to ADO and I need to
explicitly set the ref to DAO.

The message made me think that DAO was no longer supported at all.
Perhaps I misunderstood the message. So, you continue to use DAO in
your Access 2003 applications?

 

[(PeteCresswell)]

Per Dave the Wave:

So, you continue to use DAO in
your Access 2003 applications?

For the back end, depends on the app - but mostly yes.

For all my apps, I make heavy use of DAO/JET work tables - so I guess the answer
is that I use it in all my apps.