On 01/14/2012 09:29 AM, Mark Stanton wrote:
If I understand your application is to cross reference for example a
musical piece by instrumentation required, vocal parts required,
liturgical season (Advent, Lent, Easter, etc.), possibly service setting
(Holy Communion, Matins, Vespers, etc.).
Thanks for that.
Still looks a bit vague, but I haven't seen the form yet, I'll have a
This is basic database stuff that any database can/should do. The
effort of making them do it for end users will be the difference
As I said, unless someone else beats me to it, I'll have a stab at it
later (I'm also a musician, so that might help :-) )
One small step for mankind...
I would see a main table with listing each work with a unique id number
assigned to it (key). The issue is how many tables will actually be
needed for a good database design. Each table will have its own key with
any foreign keys listed for cross referencing. The basic design rule is
to enter data once and the keys establish the relation between the tables.
For a first pass at the design I would look at the data and cross
referencing used in your manual card catalogue for data relationships.
For unsubscribe instructions e-mail to: firstname.lastname@example.org
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
Impressum (Legal Info)
: 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