Consulting

Results 1 to 4 of 4

Thread: Any disadvantages in using older XML on newer Office version?

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    VBAX Contributor
    Joined
    Apr 2015
    Location
    Germany
    Posts
    167
    Location

    Any disadvantages in using older XML on newer Office version?

    Hello there,

    this is not a specific problem to solve, but something I want to learn about:

    We all start the XML code for Office 2007 with: [CODE]<customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui">[/CODE]

    And in Office 2010 and onwards we start with: [CODE]<customUI xmlns="http://schemas.microsoft.com/office/2009/07/customui">[/CODE]

    I know, I'm going to run into problems, using 2009/07 on a Office-2007-machine, but is there any danger of errors to do it the other way round? Is there any disadvantage of using 2006/01 on machines with 2010/2013/2016? If yes, which? If not, it would be easier to use ribbons with 2006/01 for both machines, in case you have, e.g., one with Office 2007 and one with Office 2013

    I usually create PowerPoint-Addins, but this might be something important for Access, Excel, Outlook, Word, too.

    Thank you for sharing your knowlegde/experiences!
    RG

  2. #2
    VBAX Sage
    Joined
    Apr 2007
    Location
    United States
    Posts
    8,744
    Location
    [CODE]<customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui">[/CODE]

    works with Office 2016 versions




    [CODE]<customUI xmlns="http://schemas.microsoft.com/office/2009/07/customui">[/CODE]

    allows some additional features to be used. Backstage is one of them



    It is possible (I believe) to have both sections in one file
    ---------------------------------------------------------------------------------------------------------------------

    Paul


    Remember: Tell us WHAT you want to do, not HOW you think you want to do it

    1. Use [CODE] ....[/CODE ] Tags for readability
    [CODE]PasteYourCodeHere[/CODE ] -- (or paste your code, select it, click [#] button)
    2. Upload an example
    Go Advanced / Attachments - Manage Attachments / Add Files / Select Files / Select the file(s) / Upload Files / Done
    3. Mark the thread as [Solved] when you have an answer
    Thread Tools (on the top right corner, above the first message)
    4. Read the Forum FAQ, especially the part about cross-posting in other forums
    http://www.vbaexpress.com/forum/faq...._new_faq_item3

  3. #3
    VBAX Contributor
    Joined
    Apr 2015
    Location
    Germany
    Posts
    167
    Location
    Thank you, Paul, this helps. As long as I don't use backstage or other new features, everything will be fine with 2006/01. It's good to know to have no disadvantages with "old" XML code.

  4. #4
    VBAX Sage
    Joined
    Apr 2007
    Location
    United States
    Posts
    8,744
    Location
    I've never found any disadvantages, but I usually keep things pretty simple and not get myself into trouble by trying to be too fancy
    ---------------------------------------------------------------------------------------------------------------------

    Paul


    Remember: Tell us WHAT you want to do, not HOW you think you want to do it

    1. Use [CODE] ....[/CODE ] Tags for readability
    [CODE]PasteYourCodeHere[/CODE ] -- (or paste your code, select it, click [#] button)
    2. Upload an example
    Go Advanced / Attachments - Manage Attachments / Add Files / Select Files / Select the file(s) / Upload Files / Done
    3. Mark the thread as [Solved] when you have an answer
    Thread Tools (on the top right corner, above the first message)
    4. Read the Forum FAQ, especially the part about cross-posting in other forums
    http://www.vbaexpress.com/forum/faq...._new_faq_item3

Posting Permissions

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