Results 1 to 8 of 8
  1. #1
    3 Star Lounger
    Join Date
    May 2002
    Location
    Smithfield, Free State, South Africa
    Posts
    210
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Convert VBA 2000 to 2003 (VBA)

    Hi there...
    We are in the process of upgrading from Office 2000 to Office 2003.
    I have noticed that some of my macros do not work <sigh>
    Is there a way that I can pre-empt this whole scenario and update my macros before they 'crash'?
    Regards

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

    Re: Convert VBA 2000 to 2003 (VBA)

    Please be specific.

  3. #3
    3 Star Lounger
    Join Date
    May 2002
    Location
    Smithfield, Free State, South Africa
    Posts
    210
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Convert VBA 2000 to 2003 (VBA)

    Hi Hans

    At the moment this is just a general query to pre-empt any problems.
    I was wondering if there were any 'rules' regarding macro changes from 2000 to 2003 versions.
    Will be more specific when I encounter an actual problem.

    Regards

  4. #4
    3 Star Lounger
    Join Date
    Apr 2004
    Location
    Boston, Massachusetts, USA
    Posts
    389
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Convert VBA 2000 to 2003 (VBA)

    You need to check your code for references to items that have changed in the Word Object Model from 2000 to 2003.

    As a more specific example (of both an item that has changed, and code that is vulnerable to that kind of change), I suggest you examine any "Not" tests in your code. I wrote a macro in Word 2000 that had something similar to the following:

    <pre>If Not styStyleVariable.Type = wdStyleCharacter Then
    </pre>


    Well, that worked fine when there were only two types of styles, but with the introduction of list and table styles, I had to revise that to be an affirmative test:

    <pre>If styStyleVariable.Type = wdStyleParagraph Then
    </pre>


    HTH

  5. #5
    3 Star Lounger
    Join Date
    May 2002
    Location
    Smithfield, Free State, South Africa
    Posts
    210
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Convert VBA 2000 to 2003 (VBA)

    mmmmm......
    Being such a novice, I will run all the macros and see where errors occur.
    Cannot be more specific at the moment. Will ask as the need arises.
    Thanks for all help.
    Regards

  6. #6
    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: Convert VBA 2000 to 2003 (VBA)

    I only do Excel VBA but know from years of messing with Excel 97, 2000, 2002 and now 2003 that it's pure hit or miss on what VBA works going from version to version. <img src=/S/brickwall.gif border=0 alt=brickwall width=25 height=15> Even if you never use any of the new features in a given version of Office (or include external references), there are still many instances where it still doesn't work (whether going to newer rev or back to older).

    There is no conversion tool but make sure you keep Word 2000 on your PC for testing purposes unless you only expect your users to have Word 2003.

    Deb

  7. #7
    3 Star Lounger
    Join Date
    May 2002
    Location
    Smithfield, Free State, South Africa
    Posts
    210
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Convert VBA 2000 to 2003 (VBA)

    Thanks for that handy tip.
    Talk about a straight up learning curve, having been thrown in at the deep end! The macro recorder is working overtime!
    Regards

  8. #8
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Convert VBA 2000 to 2003 (VBA)

    I've seen things break in Access, Excel, Outlook and Word when migrating to a newer version of Office.

    The solution is to continually enroll in the "Migrating Office VBA" course in the College of Hard Knocks.
    Most all of us get stuck in Migrating 101 and never make it to Migrating 102.
    I'm trying to get a post graduate degree in Migrating Office, but the goal seems to move with every release of Office.

    And then along came VSTO and .NET ...!

Posting Permissions

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