On 4 March 2015 at 11:25, Tom Davies <[email protected]> wrote: > 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.
Everyone can have the same frontend too (so it's keep updated) if its definition resides on the server side. Not necessarily in the same db instance or even db type. That's the way of Kexi even if "only" local SQLite instances are used. All combinations possible: local data + shared frontend, shared data + local frontend, everything shared, nothing shared. This is an entry point to the cloud infra. Without this, "splited database" with local frontend sounds still very "Access way" no matter how we criticize it. Also and idea, for a higher level operation is based on 3-tier architecture where users have access to business logic and not to physical database instances. Reasons being: reliability, maintainability and security. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek -- 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
