Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi Ian,

First, there are far more knowledgeable people responding here than I am. But here are a few thoughts from reading this thread. These suggestions are from my having used a database similar to yours for years in Open Office, and since roughly 6 months in LibreOffice since I switched from OpenOffice. I copy my database to 3 other computers running LibreOffice (I did the same thing when I was using Open Office) and I've never had any issues at all on any of the computers. So your doing it should work perfectly fine. I also don't think this is a Java issue. I'm assuming you have both LibreOffice and Open Office installed. I've never had both on the same computer at the same time. When I moved to LibreOffice, before I installed it, I removed Open Office. Maybe there is a conflict on the second computer since I see ooobuild in the path below. The second thought is maybe LibreOffice actually isn't finding your database on the second computer. I would compare your setup, paths, etc. on the first computer with the one on the second computer, and make sure on the second computer LibreOffice is looking in the right place for the database. I always have a folder under home/documents/Database where I keep my database on all of the computers.


On 09/30/2011 09:15 AM, Andreas Säger wrote:
Am 30.09.2011 14:57, Alexander Thurgood wrote:
Le 30/09/11 09:24, Ian Whitfield a écrit :

Hi Ian,

On my second machine I have a separate copy of the Database file from
machine 1 which is also "Registered" on that machine. If I try to run
the database - 'LO Base>Open existing file>Select file>Open' The Base
window opens and shows all my Tables, forms etc. But when I select any
of these I get the following error...

"Connection to 'My DB' couldn't be established.
GENERAL ERROR: org.hsqldb.lib.FileSystem RunTime Error:
Java.IO Exception:

Hmm, you are using a tinderbox build because that's what that message
seems to imply from the path ???

As the message further says, this is an IO exception :

lines 3319-3323 in xstorage.cxx deal with this and throw an exception if
the data in the container file can not be accessed.

Is your ODB file writable ?

Are you sure that the paths (and their read/write access) from the first
machine are the same as the second machine - if not, then your ODB
container as copied is going to have a problem trying resolve the paths...

The so called "database document" behaves like an extension. Every time you "open the document" the office suite extracts the HSQLDB into your temporary directory as specified in Tools>Options>Paths. Every time you "close the database document" the office suite rebuilds the package. Needless to say that this puts your data at more risk, the more data you compress and decompress.

I use to declare ~/.libreoffice/3/user/temp/ as temporary directory for the office suite. All embedded HSQLDB installs into this directory.


Don C. Myers
e-PRO Certified by the National Association of Realtors
Manager, Farm and Rural Property Division
*Coldwell Banker University Realty
*126 East Foster Avenue, State College, PA 16801
Office Phone: 814-237-6543 Fax: 814-237-6502
Home Phone: 814-422-8111 Cell Phone: 814-571-9518
Visit the Farm and Rural Property Division Web Site at <>
_View Don's Farm Web Site at <>

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.