Avatar of David Smithstein
David Smithstein
Flag for United States of America asked on

MS Word ActiveX functionality isn't allowing Embedding in OLE Field on new computer with MS Access 2013 runtime.

I have a single user who just got a new computer and now can't embed MS Word documents in the OLE field of my Access Runtime application.   At first MS Office wasn't licensed, but we took care of that and still have the problem.  I disabled click-to-run, turned off User Account Control, went into the Trust Center of MS Word and enabled All controls related to the ActiveX Settings, I also turned off Safe mode.  I disabled all but the basic Add-Ins that are working fine on my system.  We are going to test disabling Anti-virus tomorrow morning, but wanted to see if anyone could think of anything else that might be causing this effect.  I can successfully embed other document types, like MS Excel Worksheets, WordPad document, but MS Word isn't allowing the Insert Object mechanism to embed a .doc or .docx file.

When Windows makes a shortcut Word icon on his start menu, it adds those two little arrows, like a compressed folder, not sure if that's related.  Before Office was licensed, he had two little gears instead.  He is using Windows 10 Pro, MS Office 2013 without the full MS Access and click-to-run was a background process, but killing that didn't help either.
Microsoft Office* ActiveXMicrosoft AccessMicrosoft Word

Avatar of undefined
Last Comment
Jim Dettman (EE MVE)

8/22/2022 - Mon
Jim Dettman (EE MVE)

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
David Smithstein

Unable to start a DCOM Server: {00020906-0000-0000-C000-000000000046} as Unavailable/Unavailable. The error:
Happened while starting this command:
"C:\Program Files\WindowsApps\Microsoft.Office.Desktop.Word_16040.10730.20102.0_x86__8wekyb3d8bbwe\Office16\WINWORD.exe" -Embedding

Turns out the IT tech didn't want to admit a botched Office 2016 installation attempt until I found references to Office 2016 files.  So it looks like OLE is looking at a registry setting to open Word 2016 when it's not there anymore.   I don't supposed there's a registry setting for where OLE looks for Word I can fix.....?
David Smithstein

Actually WINWORD is at that file location, but at least now the IT tech has something he understands needs fixing... looks like he's going to try a roll back and reinstallation....
David Smithstein

Thanks again Jim... the perfect solution is even better when it also means someone else takes responsibility for fix it.... LOL
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
Jim Dettman (EE MVE)

Yes, those are good problems to have<g>.

 Let me know when you get to the end of the road and have it working.