LO-Base

users
#1

Hello,
I have been using OO/LO for more than a decade now and have liked it most of the
time. At the moment I have to print labels from a MySQL database connected through
JDBC. My system is Linux-Mint 17.2 and LO 5.0.2. I also use the same LO version
on a Debian 8 and Windows 7 system. I have the following problems (which I did NOT
have before):
(1) LO does not honor my action when I try to change the database source for the
DB-fields. In fact, on the labels there are 4 variables which should come from a
particular view in the database. When I specify "change database", only ONE of the
fields points to the view in the "new" database. I have tried saving/closing and
reloading the Write file that contains the references to the DB-fields, even
shutting down LO and restarting - no success!
(2) In the writer file I define a varying number of lables that should get their
data filled from an equivalent number of selected database records. I specify
"next DB-record" in the last field of every label (except of course the last label).
In the case of only 2 labels (2 DB-records), LO only prints the first one. When
I try to print 6 labels for example, it only prints numbers 1, 3, 5.
Very annoying! It always used to function without problems. I have tried things
out also on LO 4.4.5 (running on Debian, Mint, and Windows 7) -- same result.
The same also happens when connecting to the DB using the native MySQL connector.
It seems to me that Base has been a kind of stepchild in LO. To me (and my
guess is -- also to most serious users in enterprise environments), this is a
unacceptable situation.
Any help would be greatly appreciated.
H. Stoellinger

#2

Labels for label printing with mail merge fields in a Writer frontend?
A view with a SELECT statement stored in the MySQL backend?

You can change the data source name and you can change the name of the
table, view or query and then your Writer users can switch the data source
in Writer using menu:Edit>Change Source. But you should use constant fields
names. I bind all my mail merge stuff to queries with fixed column names. I
can tell my users to use a particular letter template and point it to a
distinct query within a distinct data source and everything is fine because
they find the right source for the task and the field names remain the same.

#3

Hello Andreas,
No, not labels with mail merge fields; I have for years been printing tabs for
an archive of musical notes, nothing to do with mail. To this end I have been
using a view that I created as a base for the data. I understand the process
having used it for years and years. That's why I am so surprised it doesn't seem
to work anymore. I have filed a bug in the meantime.
Regards from Salzburg
H. S.

#4

Until now I still do not understand what stopped working nor do I know
which database you are using (embedded HSQL?).