Results 1 to 4 of 4

Thread: 97 to 02 (02)

  1. #1
    Silver Lounger
    Join Date
    Dec 2000
    Location
    California, USA
    Posts
    1,758
    Thanks
    0
    Thanked 0 Times in 0 Posts

    97 to 02 (02)

    I'm in the process of switching over to XL 2002 from 97. I'm anticipating that some of the code written in 97 will not work in 02 and may need to be rewritten.

    Any suggestions as to what to look out for? I understand that no one can address all the possibilities but the top ten words of wisdom would be appreciated.

    Thanks,
    John

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: 97 to 02 (02)

    I had no problems at all when I migrated from Excel 97 to Excel 2002. Both the Excel file format and the VBA object model are compatible. Of course, there are new objects, properties, methods and events in Excel 2002 VBA, but they would only cause a problem if you wanted to use an Excel 2002 spreadsheet in Excel 97.

  3. #3
    5 Star Lounger jujuraf's Avatar
    Join Date
    Jun 2001
    Location
    San Jose, California, USA
    Posts
    1,061
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: 97 to 02 (02)

    Ok, here I go again ... <img src=/S/cranky.gif border=0 alt=cranky width=18 height=25> <img src=/S/cranky.gif border=0 alt=cranky width=18 height=25> With due respect to Hans' vast experience, I have definitely found many cases where the exact same xl97 code fails in xl2002. I also use xl2000 so have three versions to test for each release of my applications <img src=/S/dizzy.gif border=0 alt=dizzy width=15 height=15>. I find that I have to spend a huge amount of time testing my applications in all three versions. I never use any feature that isn't found in all version and I never use any external references so that means I keep everything as vanilla as possible. If a given feature (command) isn't available (such as Split in xl97) I write my own and use it instead of the built-in one.

    I tend to write large Excel applications (up to 20,000 lines of VBA so far) with a lot of fancy user interfaces, lots of forms, buttons, etc. that manipulate the data on the worksheets and do a lot of background (aka 'grunt work') for the user. You're right that there is no list of what these inconsistencies are and MS will tell you all is fine and well and no problems exist. <img src=/S/bash.gif border=0 alt=bash width=35 height=39> I've had problems with the Range.Find command across versions as well as recently finding that reprotecting (via code) a workbook in xl2002 causes the workbook to become UNprotected! I also have to add some 'on error resume next' statements for the sake of xl97 so it ignores things that the other two Excel versions handle just fine. One big thing that really gets me is that I often execute code that refers to a sheet other than the current/active sheet. Most of the time Excel97 doesn't like that. The sheet has to be active to do things to it (Excel2000/2002 don't care). I have to activate that sheet (which can cause its own problems if you have code in that event), do the code, then go back to the sheet I was on. There are quite a few more but my brain has mostly blocked out those bad experiences to keep my remaining sanity (although I did keep a list of these finds at one point...) <img src=/S/crazy.gif border=0 alt=crazy width=15 height=15>

    I've easily doubled or tripled the time it takes me to release complex applications so I wish you good luck. If your applications are small and contain mostly formulas you're probably fine. <img src=/S/2cents.gif border=0 alt=2cents width=15 height=15>

    Deb <img src=/S/flee.gif border=0 alt=flee width=25 height=25>

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: 97 to 02 (02)

    Hi Deb,

    Thanks for sharing your experience; you have no doubt written more and more complicated code in Excel than I have; I have mostly simple applications in Excel. What complicated code I write (if any) tends to be in Access.

Posting Permissions

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