Converting 97 to 2002 (2002)

Topic

New Reply

Hi I have a lot of complex databases designed in 97 which have to be converted to use in 2002. To make it more interesting, some users will still be using 97, and others will require the same d/b in 2002. Can anyone point me in the direction of any literature, and outline the (basic) steps which will need to be done in converting the databases in layman’s terms? Many thanks.

Reply | Quote

Replies

It really isn’t a very good idea to try and support both versions and A97 cannot read A2k or later at all. Although it is theoretically possible for A2k or AXP to open and run A97 databases, sooner or later *someone* converts the database instead of opening it and everyone is in trouble. A97 backends provide perfectly awful performance with A2k or AXP front ends, so that is a lousy option as well.

Reply | Quote

Unfortunately this is the strategy that Charlotte refers to as giving abysmal performance, and she is dead right. In additon, we’ve seen corruption of the back-end running in this configuration for only a month or so. If at all possible, we try to convert everyone using a given database to 2000 or 2002 at the same time. Another alternative is to convert your back-end to a more robust environment such as SQL Server before you do the front-end conversion.

Edited by WendellB at 09:59 MDT 17-Aug-02
I meant to add that there are two other current threads on this subject, and several older ones. If your database have an ancient lineage (Access 2.0 for example) you may run into other issues as well with VB or macro conversions.

Reply | Quote