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

Am 03.03.2015 um 16:06 schrieb Peter Goggin:
Much of the e-mails on Base have focussed on negative aspects. It is
worth remembering that for moderate size data bases (a few thousand
records, a dozen tables) it is perfectly adequate.  I have now converted
all of my data ase applications for MS Access to run on Base with its
internal data base. All of them perform better than they did using MS
Access. I would not regard either Base or Access as suitable for a large
multiuser data base application.  The only linux based large data base I
have developed I used MySQL with a web based front end using php to
interface to the data base.


Peter Goggin

My first medium complex project with input forms to collect daily job
data used the embedded DB as well. It worked flawlessly. But the most
important preconditions is that you really do your backup every time
after closing the connection.
Nevertheless, there are far too many reports about complete data loss.
Meanwhile it is very easy to split a self-contained Base document into a
frontend and a stable backend which can be distributed and installed on
multiple machines with a tiny little bit of extra effort. Apart from
keeping your data safe and warm, HSQL 2.3 provides a lot more features
than HSQL 1.8.

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.