Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Convert Access 97 database to 2003 1

Status
Not open for further replies.

AnnaSnowFun

IS-IT--Management
Jan 24, 2005
2
US
I have an Access 97 database that was originally written in Access 95. They now want to go to version Access 2003 and to convert all 271 references of currentdb() to ADO, and of course the code associated with all of those CurrentDB references.

My question is does someone have a good reference that explains or illustrates the difference between using CurrentDB() and ADO?

They do not want to use the 'shortcut' where the Access 3.6 library is referenced.

Any help is greatly appreciated.

Thanks.
 
Oh - moving from DAO to ADO is a bit more than replacing "currentdb";-)

You need to rewrite every usage of DAO objects to use ADO.

The exception is form recordset coding. The recordsets of Access forms are still DAO.

Consider the following familiar DAO objects:
TableDef, QueryDef, Database - they don't exist in ADO. You'll start using the connection object, the command object, and if you're going to modify queries, as with querydefs, you'll start using some of the ADOX objects, properties and methods, the catalog object would be one of them

Here's one reference Porting DAO Code to ADO with the Microsoft Jet Provider

Are you sure you won't just do the "shortcut"? BTW - lot of developers never converted to ADO, and still use DAO with all versions...

Roy-Vidar
 
And, if by chance you used the RecordsetClone and Bookmark properties of a Form, you're stuck with DAO, as even in ac2003 the form's recordset is by default a DAO object in a mdb.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244
 
Thanks for the help.

I have tried to explain that referencing the DAO 3.6 library will allow the database to be converted to Access 2003 without having to re-write the code.

They're afraid that if they don't do the conversion to ADO now, their database will not be compatible with future releases of Access.

I'll check out the references and maybe just the sheer volume of work will make them change their minds.

Thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top