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

Am 20.04.2012 10:48, Ian Whitfield wrote:
On 20/04/2012 01:18, Andreas Säger wrote:
There are not many users who suffer from the limited capabilities of
HSQL 1.8.
A high risk of total data loss is the main reason why one must not use
the embedded database. Getting an embedded database out of the jail is
easy enough.
OK Andreas (or anyone else) - for those of us not so good at this how
about a detailed Tutorial on doing this??

Right here....

1) Download and extract the latest HSQLDB to some place. No installation required. 2) Point the "Class Path" setting in the LibreOffice Java options to hsqldb.jar in your subdirectory "lib".
3) Extract the database folder out of your embedded .odb.
4) Rename the files:
 properties, script, backup, data
to:, foo.script, foo.backup,
where "foo" is just an arbitrary name.
5) Connect a new Base document to a JDBC data source with an URL like:
(the "foo" refers to the same database name I used as file name prefix)
6) Copy queries, forms and reports from the old embedded .odb to the new one.

Slightly more details and links in:

For multi-user access you can start the hsqldb.jar in server mode and connect the .odb clients with something like

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.