Upgrading from Access97 to Access2002 2

[M00ncat]

I'm working in an Access97 database that must be migrated to 2002 by the end of the year. Payroll critical information is generated by the 97 dB structure solidly in place. I've been told running 97 & 02 in parallel is unstable in the XP environment, also that a migration of this dB will not be supported by the IT department for fear that the dB's structure becomes corrupted... I've yet to figure out why this would be the case...

Feedback is much appreciated ....
Thank you!

 

[jrbarnett]

Hi,

I have not come across any Access 97 - 2002 migration problems that haven't been fixed by adding a reference to the Microsoft DAO 3.6 Object Library in the new database. No code needed editing or anything similar, but remember that this wouldn't use any of the facilities in the new version.

In the situation where your database contains company critical information I would be reluctant to do the conversion without a full Access 97 installation on a computer (which is being kept as a safety backup, not being upgraded with everyone elses) and a full backup of the database created immediately prior to the upgrade.

John

 

[mp9]

Additional possible concerns when migrating from A97 to A2000 or A2002, all of which I envcountered in a painful migration:

1. DoCmd.SendObject is buggy, so if this is used in your VBA to send e-mails you might want to rethink.

Further reading:

http://support.microsoft.com/support/kb/articles/Q260/8/19.asp

Recommended alternative:

http://www22.brinkster.com/accessory/modules/005.shtml

2. The formatted message box doesn't work either, so if you use @ in a MsgBox VBA command to get bold text formatting, you need to rethink.

Further reading:

http://support.microsoft.com/default.aspx?scid=kb;en-us;242889

Recommended solution:

http://www.mvps.org/access/bugs/bugs0035.htm

3. DoCmd.DeleteObject requires exclusive db access to run

4. As mentioned by jrbarnett, DAO is not implicitly supported - ADO is preferred. As well as adding the reference you need to make sure it is either:
(a) Above the ADO reference in your references list
or (b) The ADO reference is turned off
or (c) (Preferred) Objects are explicitly referenced in your code, i.e.

Dim dbs As DAO.Recordset

, not

Dim dbs As Recordset

Hope this is helpful.