Results 1 to 10 of 10
  1. #1
    Join Date
    Jan 2005
    Posts
    50

    Unanswered: Access 97 to Access 2003 - Conversion Help?

    I've been managing an online store database, built in access97. But now, the installation and deployment of a new RFM marketing database is requiring access 2003.

    So, I'm trying to assess all the considerations of installing access 2003. The online store simply has to be 100% operational everyday.

    I guess...my first questions is this:
    Can I run access 97 and access 2003 on the same machine? Is this problematic at all?

    If I can have both versions on the same machine, it would greatly reduce the chance of downtime regarding the online store db. I could install and finish deploying the RFM db, and take a little more time with the conversion process for the online store db.
    Who imported me here?

  2. #2
    Join Date
    Mar 2003
    Location
    The Bottom of The Barrel
    Posts
    6,102
    Provided Answers: 1
    Scary, I wouldn't do it. Any chance of running it on a virtual machine?
    oh yeah... documentation... I have heard of that.

    *** What Do You Want In The MS Access Forum? ***

  3. #3
    Join Date
    Jan 2005
    Posts
    50
    Hm, I'll have to look into that. I've never set up a virtual machine before. But, if that's a very good idea, I can definitely asked my pc techs about it.

    Any other thoughts?
    Who imported me here?

  4. #4
    Join Date
    Jan 2005
    Posts
    50
    Also, how would that work? Like I said, my problem is needing to do all of this on the same machine.

    So if I set up a virtual machine...I'd have one version one machine and the other version on the virtual machine. Would this be a permanent situation then, after that?
    Who imported me here?

  5. #5
    Join Date
    Mar 2003
    Location
    The Bottom of The Barrel
    Posts
    6,102
    Provided Answers: 1
    why do you need them to be on the same logical machine?
    oh yeah... documentation... I have heard of that.

    *** What Do You Want In The MS Access Forum? ***

  6. #6
    Join Date
    Jan 2005
    Posts
    50
    Simply because here at work, I only have one workstation.
    Who imported me here?

  7. #7
    Join Date
    Jan 2005
    Posts
    50
    And I'm not sure that I need both of them on the same machine. I just want to reduce the chances of downtime with the online store db.

    I can go ahead and install (actually, it's an upgrade) 2003 on my machine, but if there's any hold ups with the upgrade, the OLS db might be down and I really don't want that.
    Who imported me here?

  8. #8
    Join Date
    May 2004
    Posts
    159
    There is a good chance that it will run just fine under 2003.
    I would just make a copy and run it under 2003 just to test.
    with any luck all you will have to do is convert it to 2003 format.

  9. #9
    Join Date
    Mar 2003
    Location
    The Bottom of The Barrel
    Posts
    6,102
    Provided Answers: 1
    Remember that DAO reference...
    oh yeah... documentation... I have heard of that.

    *** What Do You Want In The MS Access Forum? ***

  10. #10
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926

    Access 97 and 2002/2003 on same machine

    You might want to try this on a sample mdb first. I know we had this problem with 97 and 2000 on the same machine.

    1. In either the 97/2003 mdb, import a form/report or module from another mdb.
    2. Without immediately decompiling, edit the form, add a control, add some code, and then save it.
    3. Then close the mdb, open it again, and try decompiling.
    4. If you get a nasty error, then you've encountered what I think is a rather big problem - you must immediately decompile after importing a form/report/module when you have 2 versions of access on the same box.

    Solution: See my post on having 2 versions of access on the same box.

    I'm curious if you encounter this problem with 97 and 2003 on the same machine.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

Posting Permissions

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