Migrating A97 -> A2K

[JPritch]

We are upgrading our Access 97 databases in our company since we were told that Microsoft is, or will soon no longer, support A97.

I've migrated a few of our simpler databases already. Everything went without a hitch and all functionality was retained.

Word spread and now other depts are seeking my assistance. Some of these databases are somewhat complex in regard to their use of modules and linked/ODBC tables.

If I were to attempt to convert the 97 version (copy of course), and if anything were not to convert properly, would Access tell me in the form of an error message or table? Or do I have to manually test all functionality in the 2000 version and hope that I didn't miss anything?

 

[RuralGuy]

You may find the following link useful. Converting from Access 97

 

[ghudson]

Silly for your company to upgrade to an outdated version [Access2000]. They must have found a good buy on eBay.

I know that Access 2003 will give you an errors table of anything did not convert or anything that needs to be looked at. Maybe Access 2000 will be just as kind.

 

[JPritch]

Thanks for the link...good info.

We have had A2K for quite some time now running side by side with A97, so we're not really just upgrading to it. IT has specified that they want everything to go to 2000.

I am however, going to see if some of these more complex databases that we will have a need for many years down the road, be migrated to SQL or Oracle.

 

[Robert88]

Thank you!!!!!

Hello to all who wrote this article,

I am back from the dark depths of being unemployed and now searching this forum furiously for the answer which I have found above.

Just thought I would say a quick thank you for those that wrote this article as it just saved me.

Seen the conversion question that many times just never bothered with it as I never needed it.

You guessed it, conversion between Access 97 to Access 2000. Althought I have worked up to Access 2003 I take your comments on board ghudson about the errors as I have had them before whilst reading in ASCI files into 2003. If I see any I will let you know, maybe the service Pack 3 might of addressed the issue, let you know.

Thanks everyone

Robert88