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


Hello everybody – and especially Dan Lewis.
I happened to read this thread about a database vs. spreadsheet. First of all I will thank Dan for him mentioning the “Getting Started Guide/Getting Started with Base/chapter 8"! I cannot understand how I could have missed it when I for some time have been looking for info about Base (LibreO & OOo).
It is an excellent briefing into how to build up a database using Base.

I think that you LibreO-guys should take a look at the layout where and how you introduce Base, how to get the “Getting started with Base” more visible – sort of nearer her/him who (like me) is looking for a really handy database tool. A week ago I asked your community “how get LibreO-Base working”. That is now OK (I found the JRE-file ”jxpiinstall.exe” and installed it before installing LO). Your Andreas then said that LO-Base is a front-end application, not a database. I’m not arguing but for an ordinary database consumer like me the front-end and the background database engine together mean one total database. After reading Dan’s “Chapter 8” I realized that LO-Base is The solution when a database of medium size/complexity is needed, either using the embedded HSQLDB or connecting to an external “real” database engine (e.g. MySQL or SQLite). Very much like MSAccess but free – no costs. After working some 10 years ago quite a lot with MSAccess I am a great fan of databases. Whenever I can I recommend to people not to limit to spreadsheets but build relational databases especially for their organizations but also at home. One of the great benefits compared with a spreadsheet is that you write input data only once thus minimizing both writing and writing errors - and then using the same data multiple times in different kind of reports. Another is that when a nspreadsheet is flat a (relational) database can handle data multi-dimensional which gives you the possibility to mix/combine data and get the most interesting analyzing results.
All the best
Pertti Rönnberg



On 7.2.2012 14:24, e-letter wrote:
On 06/02/2012, Dan Lewis<elderdanlewis@gmail.com>  wrote:
       Or maybe the failure is the refusal to understand the purpose for
each part of a database. Tables and forms are for adding, modifying, and
deleting data. Queries and reports are for data output. If you want to
enter data, you use a table or form. If you want to manipulate data, you
use queries. (With Report Builder, you can also manipulate data in a
report.)
Shouldn't we as users contribute to encouraging other users to always
think: what is the most appropriate use for the job? How many
questions posted are the result of making a mistake to use a
spreadsheet when a database is more appropriate?

      I wonder how many people who use LO have read chapter 8 of the
Getting Started Gude, "Getting Started with Base"? I know that I have
very seldom seen a comment about its contents. (I wrote it and am
presently updating it. I'm also working on the Base Guide in its
entirety.)

Somebody mentioned tutorials about open office base; very good
information. Maybe the authors responsible for calc should add more
conceptual advice about whether certain tasks are best performed in
base, not calc.



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