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


Hi :)
Sorry, i know it's initially more complicated but once you work it out it makes it MUCH easier for 
your normal users to use the database as they don't see any of the complexity used in the design 
process.  They just carry on using Writer.  So there is less chance of them accidentally slipping 
into design mode and stuffing things up for you.  

I forwarded this back to the User List as there was nothing to be shy about and it lets other 
people know where things are at the moment.  Also marked it solved.  
Regards from 
Tom :)  






________________________________
From: rounak jain <rounak.mint@gmail.com>
To: Tom Davies <tomdavies04@yahoo.co.uk> 
Sent: Saturday, 11 May 2013, 9:38
Subject: Re: [libreoffice-users] entering records



Your reply though not related directly to the topic is very useful and important. You are taking 
me to a completely new path raising more questions than before. Thanks, anyway for making my life 
more difficult. (By the way, I got the direct answer from the crosspost, I mentioned earlier.)




On Sat, May 11, 2013 at 1:58 PM, Tom Davies <tomdavies04@yahoo.co.uk> wrote:

Hi :)
Errr, you know you can write your reports in Writer rather than in Base?  It gives a lot more 
flexibility that way.  You 'just' need to connect your Writer document to the database.  Errr, 
that is where i get stuck though as i don't know how to do that yet! :(  

With database programs in general it is "best practice" to build Forms and Reports from Queries, 
rather than directly from Tables, because it gives more flexibility and makes it easier to fix 
if/when accidents happen (such as the back-end suddenly vanishes making the Forms freak out) or 
when the table needs to grow or change.  A Query can be a simple as "show all the data from the 
Table".  Obviously the Query itself doesn't hold any of the data, it's just an abstraction so it 
forms a buffer between the Table and the Forms and
 Reports.  It can be useful to have it do some "filtering or "sorting" so that by the time the 
Forms or Reports are looking at the data it's all neatly sorted already.  

With Base a lot of weird things go wrong when using the internal back-end to hold the data in the 
Tables.  It is really designed to be used with an external back-end.  This makes it highly 
scalable.  There are a lot of big, powerful back-ends such as MySql/MariaDB, PostgreSQL or 
smaller, lighter faster ones (although the only ones i have heard of are Java-based ones such as 
HsqlDB).  Apparently PostgreSQL has the best support in terms of their devs supporting Base 
although people on this list put a lot of work into the connectors or MySql/MariaDB and they are 
easier to contact.  Someone recently surprised me by saying that his MySql back-end was extremely 
fast so maybe it is good for small amounts of data too and not just large, hefty
 tables.  

There is some documentation about Base but it's slow going.  The most complete is on the Faq page
https://wiki.documentfoundation.org/Faq
but the handbook is getting really close too now
https://wiki.documentfoundation.org/Documentation/Publications#LibreOffice_Base_Handbook
That 2nd link also gives you the Base Guide's first few chapters which is a lot heftier as you 
will notice.  

Sorry that none of this directly answers your question!  Hopefully others will be around soon 
that can help more directly
Apols and regards from 
Tom :)  







________________________________
From: rounak jain <rounak.mint@gmail.com>
To: users@global.libreoffice.org 
Sent: Saturday, 11 May 2013, 4:28
Subject: [libreoffice-users] entering records


Three Tables:
I am writing the fields in Table.FieldName format below.

1a. Customer.ID
1b. Customer.Name

2a. Invoice.ID
2b. Invoice.Customer Name
2c. Invoice.Customer ID

3a. Invoice Details.ID
3b. Invoice Details.Invoice ID

1a, 2a, 3a are all primary fields.

Relationship one to many between:
1. Customer ID.ID ->Invoice.Customer ID
2. Invoice.ID -> Invoice Details.Invoice ID

Now, in Filemaker this was the way to use the forms:
Create a new Invoice (i.e.
 create a new record using a Form based on
Invoice Table).
Enter a value in the field Invoice.Customer Name  (a combo box populates it
with values from Customer.Name)
I have been able to reach upto here in Base.

This is the part where I need help:
In Filemaker, the Invoice.Customer ID field used to be setup as a lookup
field to auto-retrieve the Customer ID number from the Customer Table when
an entry was made in Invoice.Customer Name. The obvious purpose of doing
this is to link the Invoice and Customer table. I do not know how I am
supposed to get this done in Base. Hope I am clear. Kindly let me know if I
am not. Thank you for your time.


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






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