It would be much nicer to have a Pascal bridge rather than to support
the proprietary ActiveX protocol. Some references are on the
Freepascal wiki http://wiki.freepascal.org/Office_Automation
2017-01-23 15:42 GMT+01:00 <libroffice.dev@artavi.de>:
We are recently switched from AOO to LO. In the release notes a possible
removal of ActiveX is announced.
You are asking for information about the use case so here we are:
We are using in our company a selfmade ERP system which is grown for more
than 15 years now. For historical reasons the system is written in Delphi.
At the beginning MS Office was used as "office frontend", since about 10
years OOo/AOO/LO. The main workflow is using calc for business calculation
and writer as a kind of report tool. Most information from the main database
is delivered via ActiveX to calc. After working in calc the information are
read back and used to create documents in writer. The complete project and
document management (and many more) is done by our ERP.
I know there are others and probably more elegant ways and about once a year
we are discussing to change that and finding the "big solution" - but this
is a huge and expensive project.
Removing ActiveX from LO will be a showstopper and nail us to the last
supported release - or bring us back to AOO, who knows.
Best regards
Joergen Pisarz
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.