Hello,
A couple of versions ago of LO I mentioned that I have a problem
with serial letters using Writer and MySQL-Views through Base.
When printing a letter "populated" with database-view variables
from just ONE tuple (=record) everything is fine. Unfortunately,
when selecting MORE than one tuple for printing, various different
content of the letter gets left out in all letters following the
first on.
This might be "fixed" text (i.e. NOT from the db), graphics, but also
variables that should be included from the database.
Has anybody had the same experience?
I am now at LO 3.6.3-rc1 under Linux-Mint-Maya and use the native
MySQL-connector, but the same problem was present in earlier, stable
releases of both LO and MySQL (using a JDBC or ODBC connection).
When having to print - say - 150 letters, the fact that at present
I would have to print EVERY letter individually is unacceptable.
It certainly would prevent using LO in a business context!
I wonder whether anybody else has had the same experience.
Regards
Heinz
--
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
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
Context
- [libreoffice-users] Serial Letters · Heinrich Stoellinger
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.