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

On 11/20/2013 4:16 PM, Tom Davies wrote:

Hi :)
Sorry for the delay!  We seem to be a little slow in the last couple of weeks.

No problem. Thanks for the reply.

The 2nd table probably needs it's own ID field (yes, it's the right
term) even though it's not really going to be used at all.  Is each
row in the 2nd table unique to a Contact?  or do some contacts have
more than 1 row in the 2nd table?

I suspect that the Event Table needs to be a Query rather than a
table.  Queries look a lot like tables.  It might need to be a Form
instead though and i would build Forms by basing them on Queries.  The
Query would pull the information from both tables together then the
Form might be what you need to be able to type a name into in order to
get the details of that row of the Query.

I'm kinda clutching at straws here but i think you need to check on 3 things
1.  Give the 2nd table it's own ID
2.  Check the type of relationship linking the Connections table to
the 2nd one (ie 1 to 1, 1 to many, or many to 1, (many to many seems
3.  Try using an external back-end to store your data tables rather
than the internal one built-in

How you do that 3rd thing is still a bit beyond me but there are tools
such as Postgresql, MySql/MariaDB, HsqlDB and many others.  I don't
know which is best but it probably depends on how large the tables are
likely to be.  For any kind of contacts database it's likely to be
reasonably small so you could aim for the small, light and fast ones.

And thanks for the info. I'm off to read up on queries. I'm sure I'll have some more questions, and will ask them as they arise.


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