Legacy system Access 2.0 migration queries

[LuvSpudz]

First post, so I hope I'm following the post-etiquette!

Anyway, I've just been employed by a company who still uses access 2.0 and lotus smartsuite.

Basically I'm gonna have to migrate a few of their backbone databases to access 2000+

I've managed to find the old Microsoft access 2.0 book in the company amazingly, which is a help.

I was just wondering if anyone knows any good sites for migration, or any particular problems that may be encountered. I'm just doing some background work at the moment, this won't be happening for a few weeks (hopefully!)

Any help would be greatly appreciated.

I'll just take this opportunity to say that I've found the site very useful in the last few weeks and hope I can contribute in the future when I break out of newbie status!
-Spud.

 

[KenHigg]

The best advice I can give is to create a set of backup db's and work through the conversion a step at a time and document each issue as it arises and also document the fixes. If you encounter an issue that has you stumped, post it here in the forum...

 

[RuralGuy]

Here's some links you might find useful.
Issues in converting from Access 2
Access 2.0 Converter for Access 2003

 

[LuvSpudz]

Thanks guys.

I've been doing some searching myself and found a helpful site for migrating from lotus 1-2-3 spreadsheets to excel 2000, which I can then migrate into access tables.

Just posting it in case someone else comes across this problem.

Go here and do a search for 'migration'. You'll find it in no time.
http://www.microsoft.com/office/orkarchive/2000ddl.htm

 

[The_Doc_Man]

One issue that will zap you time and again will be the subroutine library files (.DLL files) that will be radically different in later versions of Access. The DAO, ADO, and many other external libraries have changed version numbers, which in the Microsoft paradigm appears in the file name. Like xxx35.dll becomes xxx36.dll or things like that. So your references get hosed.

I might suggest that you do NOT directly convert the databases even though it might be theoretically possible. Instead, build empty databases with your newer version of Access and then use the newer database functions to IMPORT things from the v2.0 databases. At least you will avoid SOME of the reference problems. (This won't stop you from having problems in modules that explicitly call out .DLL modules by name.)