I am attempting to upgrade an Acess 2000 database to an Access Project 

using SQL Server 7. This database has been in development for the last 8 

years, right from Access version 1, and so contains an awful lot of DAO 

based code. ADO is new to me, DAO is just the way I've always done things, 

without even realising it till now! The question is, everything I read 

says "manually upgrade the code to use ADO", but WHY? Does it just simply 

not work if I reference the "DAO 3.6 Object Library" from within the 

project? Is there a significant performance advantage to using ADO 

instead? I would like to just get the thing running and then just upgrade 

bit by bit, otherwise it will take me months! If someone could tell me why 

it is I need to re-engineer everything to use ADO I would be very 

grateful. Thanks!

Alan,



It will work just fine. You are right, get it running, and then make a move

if it makes sense.



Just one guy's opinion, of course.



Walt

Thanks Walt, but what is the criteria for it 'making sense' to do so? How 

do I know when its time to jump ship to ADO? Why would anyone employ one 

rather than the other? 

One good reason is that DAO is no longer being updated - any new functionality that Microsoft is going
to offer is going to be ADO only.



So it's worth doing just to keep your own skills up to date!



-BDS



-----Original Message-----

From:	Alan Edwards [SMTP:alan.edwards@n...]

Sent:	27 June 2001 11:03

To:	Access

Subject:	[access] Re: DAO Vs ADO?



Thanks Walt, but what is the criteria for it 'making sense' to do so? How 

do I know when its time to jump ship to ADO? Why would anyone employ one 

rather than the other?