Hi :) One point that may have become muddled in translation is that it is only the front-end that needs to be copied, or re-created on multiple machines. The stable back-end could be on a server so that everyone is using the same data. As one person adds data everyone else would be able to see that data on their various machines.
So Base is a LOT more scalable much more easily than Access. On a single machine you probably keep the back-end on the same machine as the front-end. If other machines get added then they just share that same back-end. As the company grows and eventually needs it's own internal server that back-end might get moved to that server but all the front-ends on all the different machines still keep using that same back-end even though it's been moved. Hopefully Base can even connect to back-ends hosted on WANs rather than just LANs and even on remotely hosted websites and Clouds. Regards from Tom :) On 3 March 2015 at 18:28, Andreas Säger <[email protected]> wrote: > 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. > > > > Regards > > > > > > 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: [email protected] > 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 > -- To unsubscribe e-mail to: [email protected] 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
