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

On Sun, 2012-05-20 at 01:48 +0200, Mirosław Zalewski wrote:
Sorry about pointing to another thread, but you may find this useful.
there managed to connect OpenOffice with sqlite file. I believe the
same should 
work for LO.

As far as I can tell, you will need (aside from LO, of course)
unixodbc and 
libsqliteodbc packages. At least that's how they are called in Debian;
I don't 
know about Fedora, but perhaps they have similar names. 
Thanks very much for the pointer.  I attempted to follow the
instructions, installing the SQLite ODBC Driver, but I have installation
problems. (If you configure wrong, an attempt to access a database will
lock up your system so badly that you need to reboot).  

My particular system runs KDE, which requires iodbc for many
applications, so that is what I am using for the database interface.
Iodbc has two kinds of configuration files in two places, namely:
        ~/.odbcinst.ini  (maybe not used)
The iodbc web site has info about ~/.odbc.ini, and by implication
about /etc/odbc.ini, which contains (I believe) default info; but it has
nothing about /etc/odbcinst.ini.  Can someone enlighten me about the
relation about these files and what they are used for?


For unsubscribe instructions 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.