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

Le 31/01/2012 22:07, Andreas Säger a écrit :

Hi Andreas,

Am 31.01.2012 20:16, Alexander Thurgood wrote:

Yes, the dependency on Java JRE/JDK is a pain in the backside, but
unfortunately unavoidable if you want to use Base, at least for the time

With no Java being installed, I can connect a Base document to any
non-Java database, write queries, draw input forms and use Calc as
reporting engine.

And I would state that that is an "unusual" user setup. The user here wants a relational database with subforms and reports and does not want to use mysql, so where does that leave him her with regard to Base - IMO, with HSQLDB, the stock db engine provided with LO. For that, you need a JRE/JDK.

And Calc for reports is OK, much as is Writer, but for anything a bit more than a simple report, the user will have to deal with not only the idiosyncrasies of the respective tool used for creating the report, plus, in general, learn to use macros. The whole benefit of having a specific reporting tool (the Java based ORB extension) is that this is suppose to ease that pain.

Personally, I'd love to be able to say, you get a great and easy to use db reporting engine without Java in LO, but that is simply not the case at the moment.


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.