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


Hi :)
A big
+1
Regards from
Tom :)


--- On Wed, 1/2/12, Pertti Rönnberg <ptjr@elisanet.fi> wrote:

From: Pertti Rönnberg <ptjr@elisanet.fi>
Subject: Re: [libreoffice-users] Re: How get LibreO-Base working?
To: users@global.libreoffice.org
Cc: "Alex Thurgood" <alex.thurgood@gmail.com>
Date: Wednesday, 1 February, 2012, 18:36

All of you.
Thanks very much for your kindness to bother answering - and for the very interesting discussions.

My conclusion is that LO-Base (and OO-Base ?) is not yet - and perhaps will not be as mentioned in 
the desciption at LO-Wikipedia: "A database management program 
<http://en.wikipedia.org/wiki/Database_management_program>, similar to Microsoft Access ..  etc" 
<http://en.wikipedia.org/wiki/Microsoft_Access>.
Its really pity because I think the usability of databases is underrated; quite ordinary people 
should have plenty of use of databases in their every day life if there only were free, easy 
installed, easy customized templates and some efforts on marketing. I just got a fancy idea that 
LO-/OO-Base could be that user-friendly solution.
Anyway, I still feel it worth trying to see if there should be a way to get my 32bit LO-Base 
working!

I agree. I am a 72 years "oldtimer" with a pure interest to keep up. When in office until about 10 
years ago I worked quite a lot with MSAccess and VBA & macros and got somewhat familiar with SQL 
too. MSAccess alone was enough for quite complicated projects with informative forms/reports and 
analyses.
So now it is not the MySQL/SQLite, it is the PHP-language and getting the MySQL/PHP/Apache 
combination working that I feel uncomfortable - I also have tried WASP.
Again - thanks and all the best!
Pertti Rönnberg


On 1.2.2012 9:43, Alex Thurgood wrote:
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
being.


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.


Alex




-- 
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


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.