On 1/20/2015 10:59 AM, Rich Shepard wrote:
On Tue, 20 Jan 2015, Paul D. Mirowsky wrote:
Are you using UTF-8?
Paul,
Yes.
I don't know much about your problem, but Googling shows there may be
a relationship.
See https://www.sqlite.org/c3ref/open.html
According to that web page, UTF-8
Hi :)
If using HsqlDb then it would be MUCH better to use their proper full
program downloaded from their site as an external back-end. The
in-built back-end has serious flaws which have apparently resulted in
data-loss for quite a few people so it needs frequent back-ups. As an
external back-end
On Wed, 21 Jan 2015, Tom Davies wrote:
If using HsqlDb then it would be MUCH better to use their proper full
program downloaded from their site as an external back-end.
Tom,
OK. Guess I need to download, build, and install a 3rd rdbms. That's
do-able. Lots of room on this partition.
I as
On Wed, 21 Jan 2015, Alexander Thurgood wrote:
The hsqldb 1.8 documentation ? LO uses the hsqldb 1.8 as the embedded db
engine in LO by default, unless you meant you are setting up a "split"
database using an external hsqldb.jar version > 2 ?
Alex,
The manual appears to be the most current,
Le 21/01/2015 16:54, Rich Shepard a écrit :
>
> There's actually a better, easier, quicker solution. I downloaded the
> hsqldb user guide (not the Base Handbook) and learned that I can write the
> schema and read it into a database then set up Base to use it. The guide
> includes the supported
On Wed, 21 Jan 2015, Tom Davies wrote:
If the problem is the lack of a connector then writing a connector in
Python so that you can use Base might be more useful than developing your
own database program to use the sqlite backend - especially if you
OpenSource the connector and upload it to the
Hi :)
If the problem is the lack of a connector then writing a connector in
Python so that you can use Base might be more useful than developing
your own database program to use the sqlite backend - especially if
you OpenSource the connector and upload it to the Extensions website.
It'd mean more p
On Mon, 19 Jan 2015, Rich Shepard wrote:
One of the unixODBC developers has been helping; perhaps tomorrow (in my
timezone) it will finally be resolved.
Apparently there's no visible explanation for the problem. So, I'll write
the application in Python/wxPython which I know works well with s
On Tue, 20 Jan 2015, Paul D. Mirowsky wrote:
Are you using UTF-8?
Paul,
Yes.
I don't know much about your problem, but Googling shows there may be a
relationship.
See https://www.sqlite.org/c3ref/open.html
According to that web page, UTF-8 is the default for sqlite3_open() and
sqlite
Shot in the dark.
Are you using UTF-8?
I don't know much about your problem, but Googling shows there may be a
relationship.
See https://www.sqlite.org/c3ref/open.html
Hope this helps
On 1/19/2015 5:16 PM, Rich Shepard wrote:
On Tue, 20 Jan 2015, tonybsa wrote:
Yes I was aware of this bu
On 20/01/2015, at 9:16, Rich Shepard wrote:
> Tony,
>
> With the help of one subscriber to the unixODBC mail list we may have
> found the problem source.
> dltest /usr/local/lib/libsqlite3odbc.so SQLConnect
Good to know that there is a solution.
Perhaps the documentation team can find time
On Tue, 20 Jan 2015, Andreas Säger wrote:
Your tables, relations, indices and data are still in the SQLite.db file
and handled by the ODBC driver. The so called Base document is just a
configuration file with optional queries, forms and reports. It is bridge
between SQLite and office documents.
Am 18.01.2015 um 18:43 schrieb Rich Shepard:
> Than, when I clicked the 'Finish' button I get a LO save dialog with the
> default name of 'New Database' (with a space that needs to be removed, no
> less!). If I give it a name, does the new *.odb contain the schema and data
> of the existing sq
On Tue, 20 Jan 2015, tonybsa wrote:
Yes I was aware of this but thought that just "maybe" the oracle drivers
would work for you. Sorry all out of other suggestions.
Tony,
With the help of one subscriber to the unixODBC mail list we may have
found the problem source. Results of two tests:
[
On 20/01/2015, at 8:08, Rich Shepard wrote:
> Tony,
>
> I've done this several times, but the only drivers visible are for sun
> (now oracle) star. See attached .png.
Yes I was aware of this but thought that just "maybe" the oracle drivers would
work for you.
Sorry all out of other suggestio
On Mon, 19 Jan 2015, Rich Shepard wrote:
I've done this several times, but the only drivers visible are for sun
(now oracle) star. See attached .png.
Apparently, attachments are stripped off. But there are only the sun
drivers visible and no button to add others.
Rich
--
To unsubscribe e-
Rich Shepard schreef op 19/01/2015 om 20:40:
On Mon, 19 Jan 2015, Rich Shepard wrote:
LO-4.3.5, unixODBC-2.3.2, and sqliteodbc-0.9991, and sqlite-3.8.8 on
Slackware-14.1. I use the build scripts provided on SlackBuilds.org,
except
for sqliteodbc which I built with the usual configure; make; ma
On Tue, 20 Jan 2015, tonybsa wrote:
You may need to go to "LibreOffice > Tools > Options > LibreOffice Base >
Connections" and select the "ODBC Driver", under the "Connection Pool"
dialogue. Select the driver and click the "Enable pooling for this driver"
checkbox.
Tony,
I've done this seve
On 20/01/2015, at 6:40, Rich Shepard wrote:
> "The connection to the data source '' could not be established.
> "[unixODBC][Driver Manager] Data source name not found, and no driver
> specified."
> What am I doing incorrectly here?
You may need to go to "LibreOffice > Tools > Options > Libr
On Mon, 19 Jan 2015, Rich Shepard wrote:
LO-4.3.5, unixODBC-2.3.2, and sqliteodbc-0.9991, and sqlite-3.8.8 on
Slackware-14.1. I use the build scripts provided on SlackBuilds.org, except
for sqliteodbc which I built with the usual configure; make; make install.
Some progress has been made. Th
On Mon, 19 Jan 2015, Alex Thurgood wrote:
Which version of LO are you using? A distrib provided one, a TDF
download? I don't know whether there is a difference in the library
versions that the various package maintainers / TDF chooses for unixODBC
when they build LO. There is certainly a build s
Le 18/01/2015 23:07, Rich Shepard a écrit :
Rich,
>
> 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 confi
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"
Tony,
Thought this to be the case.
LibreOffice Base can be a database!! but in your case the database is
SQLlite and the L
On 19/01/2015, at 4:43, Rich Shepard wrote:
> Step 4 is 'Save and Proceed' which is where my choices do not produce the
> result I expect.
>
> The top portion of the dialog box has 2 radio buttons: do I want to
> register the database with Base? I assume so, but the help button moves the
> ope
24 matches
Mail list logo
