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


Hi Alex,
Thanks for the information! Actually, I use 3.6 on my "production" Laptop and can
therefore produce my reports without problems. On the other hand, deskop integration
under 4.1.0-RC4 on my KDE 4.10 system still doesn't work. So I will wait with reports
on 4.1 until this aspect is fixed. No crisis...!
Regards
H


On Wed, 24 Jul 2013 18:18:25 +0200, Alexander Thurgood <alex.thurgood@gmail.com> wrote:

Le 24/07/13 18:13, Heinrich Stoellinger a écrit :

Hi Heinrich,

Hello,
I am trying to use LO 4.0.4 on my Linux-Debian-Wheezy system. Most
things work
o.k., except when I try to run a report based on a view within a MySQL
DB, LO
crashes momentarily. The same reports run without problems under 3.6.6.

This is a known bug of LO 4.0.4, which has already been fixed in the
upcoming release of LO 4.1. In the meantime, you can go back to LO
4.0.3, where that functionality still worked.


Alex





--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/

--
To unsubscribe e-mail to: users+unsubscribe@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


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.