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

Hi :)
Thanks for your support chaps! :)

I think the main problem was about HSqlDb being fairly fantastic as a
back-end when used as an external back-end, preferably as their latest
version from their official website (or your distro's repos or whatever)
but any of their versions will do apparently;
Their 2.3.2 does full multi-threading.  "The latest version 2.3.2 improves
on access and management of very large data sets. It supports up to 270
billion rows of data in a single database and a hot backup capability."

Ok, so it seem my thoughts about it being mainly for small, light and very
fast databases was "a bit off" too!  I'm not sure how that compares with
MySql/MariaDb or Postgresql but it sounds like, as almost always ime, the
simplest explanation to cover all available information is not always the
truth!  HSqlDb seems good for rather large databases after all.

Also it sounds as though it is reasonably easy to export a ".jar" file (or
something) from Base, if you are currently using the internal back-end and
then just use that in an external version of HSqlDb then that works quite
well too apparently.  This is something i wish had been clear many years

So the only problem is with continued current usage of the internal
back-end but having easy migration routes into external back-ends might
help us deal with people's problems MUCH more easily in the future.  Does
anyone here have a database that does still use the internal back-end?  If
so is there any chance of experimenting with exporting as some sort of java
file with maybe a little help from some of the experts on this mailing
list?  I would be interested to see how it plays out and whether it really
is as easy as has been suggested.

Right now my feeling right now is that moving to MySql/MariaDb still has
advantages, such as possibly being more widely used and therefore maybe
easier to get advice, guidance and maybe even training in.
Regards from
Tom :)

On 5 March 2015 at 17:36, SOS <> wrote:

On 5/03/2015 16:04, Stefan Geith wrote:

Hi :)

I'm working with FilemakerPro since it was available for Windows (1995)
for Standalone-Databases. I'm working with PHP and mySql since 1998 and
with Typo3 (using PHP and MySql) since 2002.
I always used FilemakePro for all kinds of single-user databases, e.g.
Address_lists, Invoices, etc. and later (beginning with FileMaker Pro 7.0)
I used it as a Frontend for MySql.

But unfortunately Filemaker ist not available for Linux, only for
Mac+Windows, so some days ago I gave LibreOffice Base (4.4) a try, did some
tutorials and now I'm very exited about its possibilites - especially the
use of direct mysql-queries (thats not possible with FileMaker).

But in LibreOffice Base there are some (in my opinion very important)
things missing:

1. I cannot use the internal LibreOffice Database together with an other
external (e.g. Mysql-) Database.
With Filemaker I often created local (Filemaker-) Databases, containing
search-filters (or settings) for the local user that filter the lists of
the mySql-Data-Forms. This seems not possible with LO Base.

2. LO Base is missing options to create apps for 'simple' users.
Using a LibreOffice Base file is too complicate for many users who simply
have to add/edit data. I know, there are standalone-forms, but there are
too few possibilities with that (e.g. no Macros).
For a 'simple' user, I'd like to have
- *one* Window and buttons to switch the content of the window to
different forms/reports etc.
- a tab-controller element (switching through subforms with tabs)
- a script-engine easier to use than macros (see FileMaker how this can
be made perfectly)
- Security-Settings/User-Rights, so that users cannot destroy their app
by mistake

This year, I have to create a frontend for a really big MySql-Database
(100+ Tables). There is a web-app to browse this data, but for
adding/editing data there is no perfect solution yet (This customer uses a
php-import-script for his Access-Databses atm...)

I would really like to implement this frontent with LO-Base, but I'm
afraid I will end up with Filemaker because I can create a more robust tool
with it (and also, because I'm used to it since years...)

LibreOffice base will bring not real new stuff due to lack of developer
interest, but you can perfectly build yourseff a frontend using the API and
basic. Keep away from "forms" and use Dialogs instead.


I'm curious to see what will be new in the next versions of LibreOffice


Maybe I'm wrong with the results of my test and all/some of these options
already are possible - if so, please let me know ;)

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

To unsubscribe 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.