How to reproduce the bug :
- install LibO and create a simple ods,
- open Microsoft Word,
- insert > Object > "create from a file",
- choose the ods file.
The ods is include as a icon.
- install OpenOffice,
- retry to insert the document in Word.
I don't know if it's a Word or a LibO bug but I guess it's related to the LibO installer.
I already try to modify the registry to force Word to insert ods files as OLE elements (I tried to match the LibO install to the OpenOffice install) but my modification make Word crash…
In fact, I just try with WordPad and it doesn't work either, so it's not . It seams the whole OLE part of the installer is broken…
- In fact, I just try with WordPad and it doesn't work either, so it's not .
+ In fact, I just try with WordPad and it doesn't work either, so it's not a Microsoft Word bug.
Hi, i have the same problem.
I try to embed an opendocument in a standalone application that use OLE controls.
I try to embed, link or create new opendocument in a OLE control, but every test fails.
Please, i don't want to install openoffice because i like libreoffice and their philosophy.
It seems it’s related to activex components which have been disabled on the official released since it creates more bug than it solves.
Thanks for your comment.
So, if i want to embed opendocument in any application or other document, i must install openoffice? Very sad thing...
It is true that embedding OLE objects feature (more precisely the needed registry settings) was bound to the ActiveX component that we don't install by default, but in fact it is not necessary to have that ActiveX component for OLE embedding.
I'm not sure what problems can occur, if I enable those registry settings unconditionally. Please test.
Andras Timar committed a patch related to this issue.
It has been pushed to "master":
fdo#47944 enable insertion of OLE objects into external applications
*** Bug 48757 has been marked as a duplicate of this bug. ***