I've got to go with Arend on this one, since a 32-bit platform will only have a "Program Files" path.. MS might have done better to name the new folder "Program Files(x64)". \:\)

Something like this will work but doesn't validate the presence of the 32-bit app:
 Code:
If %PROCESSOR_ARCHITECTURE% = 'x86'
  'Office 32bit' @CRLF			; Can't be 64-bit on x86 platform
Else
  ; 64-bit platform - see which version of Office is present
  If Exist('C:\Program Files\Microsoft Office\Office15\WinWord.exe')
    ; app found in 64-bit location, is x64
    'Office 64bit' @CRLF
  Else
    'Office 32bit' @CRLF
  EndIf
EndIf
As a UDF, which returns 0 (not found), 32, or 64:
 Code:
Function OfficeBits()

  If %PROCESSOR_ARCHITECTURE% = 'x86'
    $OfficeBits = 32			; Can't be 64-bit
  Else
    ; 64-bit platform - see which version of Office is present
    If Exist('C:\Program Files\Microsoft Office\Office15\WinWord.exe')
      ; found in 64-bit path
      $OfficeBits = 64
    Else
      If Exist('C:\Program Files(x86)\Microsoft Office\Office15\WinWord.exe')
        $OfficeBits = 32      ; found in 32-bit path
      Else
        $OfficeBits = 0       ; not found!
      EndIf
    EndIf
  EndIf

  Exit 0

EndFunction
For a proper function, the install path should probably be gleaned from the registry. This still isn't foolproof as I can do a custom install to, say, "D:\Programs" that will render this method useless. It's probably OK for most of the installations out there.

The WMIInstalledProducts UDF (download from my web site) returns the product GUID. If the "Microsoft Office" product is found, there is a value in the GUID that returns the product bitness.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D