Results 1 to 4 of 4
  1. #1
    Star Lounger
    Join Date
    Mar 2002
    Location
    Edinburgh, Scotland
    Posts
    80
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Converting 97 to 2002 (2002)

    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.

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Converting 97 to 2002 (2002)

    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.
    Charlotte

  3. #3
    eLar
    Guest

    Re: Converting 97 to 2002 (2002)

    Another strategy you might take is to split your database into a front end (with all the forms and reports) and a back end (with all the data). Leave the back end in 97 format and put it on your network. Take the front end and make a copy. Leave the 97 copy for the Access 97 folks, linking it to the data in the back end copy. Convert the copy to 2002 and again link to the data in the back end. Make sure that the 2002 folks don't mess with the 97 front end. You'll then have two copies of the front end that will need updates, but everyone should be able to use it.

    -Larry

  4. #4
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Converting 97 to 2002 (2002)

    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.
    Wendell

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •