Results 1 to 3 of 3
  1. #1
    4 Star Lounger
    Join Date
    May 2003
    Location
    Austin
    Posts
    401
    Thanks
    0
    Thanked 0 Times in 0 Posts

    97 to XP (97-SR2)

    I just heard that our entire system is going to change from NT 4.0/Office 97 to XP/Office XP.
    What kind of changes in regard to ease of development, can I look forward to seeing?
    On the flipside, what surprises might be in store?
    Will the IS section be able to strip any functionality out of it, before deployment ? <img src=/S/cauldron.gif border=0 alt=cauldron width=20 height=20>

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

    Re: 97 to XP (97-SR2)

    I would start looking at the various forums on WOPR - the workstation upgrade to XP will be the Professional version I presume, which is from the NT4/W2000 lineage, so it shouldn't be too different. But Office XP is quite a departure from 97. Access in particular is from the 2000 vintage, which is quite different from 97 as well. Databases will need to be converted to either the 2000 or the 2002(XP) format in order to do any maintenance work. That can be a sizeable effort, though most things covert pretty cleanly. You might want to read the WOW newsletter that came out today on the issuing of an XP Service Pack on 12/13 as well. I've been using XP for several months, and it seems to be pretty stable, but there are some specific issues with Mail Merge and with running 2000 and XP on the same system. Others may want to chime in here too.
    Wendell

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

    Re: 97 to XP (97-SR2)

    Probably the biggest difference you'll see in Access XP is the shift from the DAO object model to ADO as the default. Most of us who work with 2000 have already faced that hurdle, but it will be new and different to you. You can still use DAO in 2000/2002, but you have to specifically set the reference and then get used to specifying the object model in your declarations, i.e., DAO.Recordset rather than just Recordset. Your converted databases will have the reference set, but any new ones you create will default to ADO, which is *very* different from DAO. XP is also more XML oriented that 2000, and 97 thought it was a misspelling <img src=/S/grin.gif border=0 alt=grin width=15 height=15>, so that's another learning curve for you.
    Charlotte

Posting Permissions

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