On Mon, 19 Jan 2015, tonybsa wrote:
It is a good idea to register the database as then the data is accessible
to the Writer and Calc programs under "View Data Source"
Thought this to be the case.
LibreOffice Base can be a database!! but in your case the database is
SQLlite and the LibreOffice Base is just a way of working with the data
from the SQLlite database. When you save the newly created connection to
the database by giving your Base file a name you are in fact creating the
front end, NOT a database!!
Wondered about this so I went ahead and created a file with the .odb
open it you will find all your SQLlite tables, views, procedures, etc.
displayed in the front end and you can then edit or work with the data in
the SQLlite database. If your connection to the database is good you can
now control the input and extracion of data using your Base front end.
Ah, but here's the problem: Base is looking for libsqliteodbc.so which is
specific to SQLite2. Since SQLite3 has been out a few years now, I looked
for a way to tell Base the library is called libsqlite3odbc but could not
find a configuration option.
On the one hand, I can make a soft link from /usr/local/lib/sqlite3odbc.so
to /usr/local/lib/sqliteodbc.so, but that won't work for the users on
If someone points me to the way of telling Base that the library is for
SQLite3, I'll make the fix and move on with the project.
To unsubscribe e-mail to: firstname.lastname@example.org
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
Impressum (Legal Info)
: 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