• 97 to XP Migration (97 and XP)

    Author
    Topic
    #406480

    Hi all,

    I am currently involved with a roll out of Office XP. As such I have to write a little application that will scan through Access Databases and identify problems both pre and post rollout. Adding to the complexity the server drive mappings will change twice during the rollout (yes server names are changing so UNC paths will break as well).

    It is intended that this app be used for user hard disk drives. As such I don

    Viewing 3 reply threads
    Author
    Replies
    • #843205

      If you do a search in this forum for convert 97, you’ll find numerous older threads dealing with the conversion from Access 97 to Access 2000/2002/2003. Many issues will be difficult to handle in batch.
      Some things to look for:
      – Making implicit DAO declarations explicit (Dim rst As DAO.Recordset instead of … As Recordset)
      – Bracketing of query parameters ([Forms]![frmSomething]![txtStart] instead of Forms!frmSomething![txtStart])
      – Modifying code for formatted MsgBox (using @ in the prompt text doesn’t work any more)
      – Merging data to a Word document has changed.

      • #843704

        Hans,

        Thanks for that.

        I have searched and read lots of messages in the forum and read the MS whitepaper on access conversion and converted about a dozen systems of various complexity to XP.

        No what I am doing is trying to develop a tool to first identify possible problem databases in 97 and then to convert and flag databases that have conversion problems.

        I don’t know that I will be fixing DAO syntax as part of the batch, I suspect that if there are any user built systems with DAO code I will probably want to have a look to determine what the system does.

        As the tool will be given to end users,help desk personnel, and floor walkers during the roll out as a first line of anaylsis I’m just trying to determine if there are any other things that I can check and fix via batch processing.

        I know my most important result from this tool (as the second line of support) will be the log of systems processed and those flaged for manual intervention.

        Stewart

      • #843705

        Hans,

        Thanks for that.

        I have searched and read lots of messages in the forum and read the MS whitepaper on access conversion and converted about a dozen systems of various complexity to XP.

        No what I am doing is trying to develop a tool to first identify possible problem databases in 97 and then to convert and flag databases that have conversion problems.

        I don’t know that I will be fixing DAO syntax as part of the batch, I suspect that if there are any user built systems with DAO code I will probably want to have a look to determine what the system does.

        As the tool will be given to end users,help desk personnel, and floor walkers during the roll out as a first line of anaylsis I’m just trying to determine if there are any other things that I can check and fix via batch processing.

        I know my most important result from this tool (as the second line of support) will be the log of systems processed and those flaged for manual intervention.

        Stewart

    • #843206

      If you do a search in this forum for convert 97, you’ll find numerous older threads dealing with the conversion from Access 97 to Access 2000/2002/2003. Many issues will be difficult to handle in batch.
      Some things to look for:
      – Making implicit DAO declarations explicit (Dim rst As DAO.Recordset instead of … As Recordset)
      – Bracketing of query parameters ([Forms]![frmSomething]![txtStart] instead of Forms!frmSomething![txtStart])
      – Modifying code for formatted MsgBox (using @ in the prompt text doesn’t work any more)
      – Merging data to a Word document has changed.

    • #843254

      In addition to Hans’ comments, there are a couple of other issues to sort out. One is what format databases will be stored in. One school of thought says that the 2002 format has some technological advantages, while another says that 2002 format databases bloat much more than 2000 format databases. Another consideration is that if you end up with a few people running Access 2000, they would not be able to open 2002 format databases.

      Also, you might be interested to know about a new product called “The Access Conversion ToolKit” about to be released by Microsoft. It was described at Tech*Ed 2004 at the end of May, though there was some informal information available prior to that. It focuses on conversion to Access 2003, but should be more or less equally applicable to 2002. You can read more about it on this Microsoft webpage.

      • #843706

        Wendell,

        The issue of version is a good one and I think we are happy with te 2k format.

        I was aware of the “The Access Conversion ToolKit” as I found reference to it in a search here. I got very excited and if it was available now it would be just what I need. But released later this summer (winter for us) isn’t specific enough for me to rely on it becoming avaialable within a time frame that is useful.

        Thanks for taking the time to reply.

        Stewart

      • #843707

        Wendell,

        The issue of version is a good one and I think we are happy with te 2k format.

        I was aware of the “The Access Conversion ToolKit” as I found reference to it in a search here. I got very excited and if it was available now it would be just what I need. But released later this summer (winter for us) isn’t specific enough for me to rely on it becoming avaialable within a time frame that is useful.

        Thanks for taking the time to reply.

        Stewart

    • #843255

      In addition to Hans’ comments, there are a couple of other issues to sort out. One is what format databases will be stored in. One school of thought says that the 2002 format has some technological advantages, while another says that 2002 format databases bloat much more than 2000 format databases. Another consideration is that if you end up with a few people running Access 2000, they would not be able to open 2002 format databases.

      Also, you might be interested to know about a new product called “The Access Conversion ToolKit” about to be released by Microsoft. It was described at Tech*Ed 2004 at the end of May, though there was some informal information available prior to that. It focuses on conversion to Access 2003, but should be more or less equally applicable to 2002. You can read more about it on this Microsoft webpage.

    Viewing 3 reply threads
    Reply To: 97 to XP Migration (97 and XP)

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: