Le 07/06/2016 à 20:11, Christopher Howard a écrit :
Hi Christopher,
Hi, I want to create a small embedded Base db for 3 or 4 users. It is a
mix of Gnu/Linux and Windows desktops. I can create a Base db just fine
on my person Debian laptop, but if I try to create it on our Windows
share, or copy it there and then use it, I get an error that Base cannot
communicate with the database. I can read/write to the share fine with a
file manager or text editor... so I am thinking this has something to do
with the nuances of NTFS, or file locks, or something like that. Does
anyone have any insight on that, and related work arounds?
Thanks for letting me know about your setup (I guess you used reply only
to me because I didn't see it appear on the mailing list).
I have just created an embedded hsqldb ODB file (i.e. the default ODB
type) with LO 5132 on OSX 10.11.5, in which I saved the ODB file to a
SMB share hosted on a Linux Mint 17.3 server. I can open, read, and
write to the file from either the LM server or the Mac OSX client.
My guess would be that the issue lies with your Win 2008 server.
Alex
--
To unsubscribe e-mail to: users+unsubscribe@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
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.