Supercharge your PowerPoint productivity with
Supercharge your PPT Productivity with PPTools - Click here to learn more.

PPTools

Image Export converts PowerPoint slides to high-quality images.

PPT2HTML exports HTML even from PowerPoint 2010 and 2013, gives you full control of PowerPoint HTML output, helps meet Section 508 accessibility requirements

Merge Excel data into PowerPoint presentations to create certificates, awards presentations, personalized presentations and more

Resize your presentations quickly and without distortion

Language Selector switches the text in your presentation from one language to another

FixLinks prevents broken links when you distribute PowerPoint presentations

Shape Styles brings styles to PowerPoint. Apply complex formatting with a single click.

Prep4PDF preserves interactivity in PowerPoint presentations when you convert to PDF

Programming for 64-bit vs 32-bit Office 2010

Office 2010 and later bring the option of installing a 64-bit version, which may cause compatibility issues for add-ins written for 32-bit versions of Office.

Here's detailed information from Microsoft about the differences:

Compatibility Between the 32-bit and 64-bit Versions of Office 2010

Office 2010 also gives us a couple of new compiler constants that we can use to determine whether we're running a new version of Office that includes these constants, which "bitness" of Office and, indirectly, which Windows bitness we're running.

The most useful of these constants is Win64. Oddly, it actually tells us which "bitness" of Office we're running in. If Win64 is True, then it's 64-bit Office (which implies 64-bit Windows, since 64-bit Office won't run in 32-bit Windows).

Most people don't believe me when I say this. After all, why would Microsoft call it Win64 instead of Office64 if this were true?

I have no idea. But they did. The code proves it:

Sub WhichVersion()

    ' The Win64 constant is a misnomer
    ' It doesn't tell you anything about the "bitness" of Windows
    '   (well, indirectly it does; more on that anon)
    ' It DOES tell you the bitness of OFFICE
    '
    ' Run this under Windows 7/8/etc. 64-bit and
    ' Office 32 and it'll tell you it's NOT Win64.
    '
    #If Win64 Then
        Debug.Print "It says that this IS Win64"
        Debug.Print "It really means that this is 64-bit OFFICE."
        Debug.Print "(And 64-bit Windows, since 64-bit Office requires that.)"
    #Else
        Debug.Print "It says it's NOT Win64"
        Debug.Print "It really means that this IS NOT 64-bit Office."
        Debug.Print "(It might be 32-bit Office on 64-bit Windows, though.)"
    #End If
    '
    ' But indirectly, there's this:
    ' If #Win64 is true, then it IS Windows 64-bit, because:
    '   - It's Office 64-bit,
    '   - Which only runs under 64-bit Windows

    #If VBA7 Then
        Debug.Print "VBA 7, so it must be Office 2010 or later"
    #Else
        Debug.Print "NOT VBA7, so Office 2007 or prior"
    #End If

End Sub

If using an older version of Office, these compiler constants won't be defined, so they'll return False. It's perfectly safe to use them this way.


Did this solve your problem? If so, please consider supporting the PPT FAQ with a small PayPal donation.
Page copy protected against web site content infringement by Copyscape Contents © 1995 - 2015 Stephen Rindsberg, Rindsberg Photography, Inc. and members of the MS PowerPoint MVP team. You may link to this page but any form of unauthorized reproduction of this page's contents is expressly forbidden.
Español    Deutsch    Français    Português    Italiano    Nederlands    Greek    Japanese    Korean    Chinese

Supercharge your PPT Productivity with PPTools

content authoring & site maintenance by
Friday, the automatic faq maker (logo)
Friday - The Automatic FAQ Maker

Programming for 64-bit vs 32-bit Office 2010
http://www.pptfaq.com/FAQ01065_Programming_for_64-bit_vs_32-bit_Office_2010.htm
Last update 08 April, 2015
Created: