For anyone following along, I've managed to make it past the most basic of problems with object creation. Looks like I had some registry conflict because I had parts of Office 2010 installed (Access, Visio). I uninstalled 2010 which then completely broke COM. Finally I followed that up with a quick repair of O2016 and could once again create COM objects. Now I can go back to working on the thing that I really wanted to do.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, December 05, 2016 12:10 PM To: profoxtech@leafe.com Subject: COM Automation problem with Word 2016
Whilst I bang away at this on my own I figured I should throw it out to the collective wisdom. I noticed recently that both CreateObject and NewObject are failing to instantiate an object for Word 2016. GetObject works fine to retrieve a running instance. Excel works fine.
oo=CREATEOBJECT([word.application])
results in OLE error code 0x80080005: Server execution failed.
Google fu has failed me so far. If anyone here has had success automating Word 2016, please share your magic tricks.
Thanks.
--
rk