viewpoint-particle

Author Topic: Office 2019 64 bit  (Read 65 times)

stanl

  • Pundit
  • *****
  • Posts: 796
Office 2019 64 bit
« on: October 16, 2018, 03:33:48 am »
Decided to give it a try, mainly for the updated Excel features. It installed as 64 bit after I removed Office 2016. When I tested the Ace.Oledb.16.0 Provider my WB script returned an error that the provider may not be installed correctly. However, running the script as WB 64bit worked. But I swear my 2016 was installed as 64 bit and WB 32 bit scripts worked.


This is not work related, or for development - mainly for personal interest. For fun, I tried re-installing 2019 as 32-bit but it complained that was not possible as the system had a number of 64 bit stuff installed.  Guess I'm having a Rip Van Winkle moment :o [size=78%] [/size]

td

  • Tech Support
  • *****
  • Posts: 2618
    • WinBatch
Re: Office 2019 64 bit
« Reply #1 on: October 16, 2018, 07:20:09 am »
You definitely need to use 64-bit WinBatch with 64-bit Office COM Automation objects.  I know that I have used officially unsupported techniques to install some 64-bit Office COM services on a system with 32-bit Offices already installed but that was with an older version of Office.  I guess the only point being that it is possible to have both 32-bit and 64-bit Office COM Automation objects available on a system and that may (or may not) explain why you could use both 32-bit and 64-bit Office COM servers on the same system.
"Success is a lousy teacher. It seduces smart people into thinking they can't lose."
  - Bill Gates


stanl

  • Pundit
  • *****
  • Posts: 796
Re: Office 2019 64 bit
« Reply #2 on: October 16, 2018, 08:51:33 am »
Not to appear second guessing, but when I had 2016 installed the 2007 Access Objects were still there. I couldn't use Ace.OLEDB.14.0, but 12.0 seemed to work (as I looked at my old script). 2019 wouldn't install until I removed all 32 bit stuff. No use taking it any further, but if other OP's in this group end up loading 2019 I can help test any issues. Thanks TD!