Hello,
I am developing a tool that in the batch mode trough UNO generates a scalc documents. Users have to
have an ability to open generated and saved documents.
On the windows I can start office as a server (in the background mode) using either of the commands
start soffice -headless -nologo -nodefault
"-accept=socket,host=0,port=8100;urp;StarOffice.ServiceManager"
start soffice -invisible -nologo -nodefault
"-accept=socket,host=0,port=8100;urp;StarOffice.ServiceManager"
Using my application I can generate and save output document. But when I try to open it the command
just returns back doing nothing.
When I kill soffice background I can open any saved document but I can't generate any new one till
I start soffice in the background again.
So I can't to do both background and foreground work at the same time. When I am working with
Microsoft excel I have no such problems at all.
Could you help me to solve the problem?
Sergey.
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] How to use LibreOffice on ms windows as a background server and in interactive mode at the same time? · Сергей Мосин
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.