What you list for columns D, E, F, G,H,I are not tables. They are reports
for the table "Reaction".
Your primary data point is reaction. It has the parameters of actor and
observer, date/time, location, and whatever ratings or review information.
Then you build a report based on the "observer" table that provides the
D,E,F data. I'm not clear if the time (Days, Weeks, Months) is part of DEF
list, or another list. Probably its more calculations on the Same
information in the report.
On Tue, Feb 4, 2020 at 12:52 PM Robert Großkopf <robert@familiegrosskopf.de>
wrote:
Hi David,
Only one some hints for the tables and the relations between the tables:
A. ID
B. Name <text>
C. Gender <text>
D. Number of reactions done <number>
E. First reaction <date>
F. Last reaction <date> this is the most recent reaction
G. Days - Formula =NOW() <cell ref>
H. Weeks - = <cell ref/7>
I. Months = <cell ref/4)
This has worked very well but now I want to be able to gather more
information using just Columns A, B, C. So, what I can gather from
reading
the Getting started instructions for Base, I need more than one Table.
Are
those listed below suitable.
Table 1 - Reactors
ID
Name
Gender
Table 2-Performers
ID
First name
Last name
Do you need Table 1 and Table 2? Could also be one table all together
wit a field, which shows 'R' for Reactors and 'P' for Performers
Table 3 - Performance
ID
Title (this eill be the title of a song, or a dance routine, or a piano
concerto, etc.
Date upload
Website
There must be a foreignkey from the Performers to the Performance. The
"ID" form Performers has to appear at "Performance" as "Performers-ID",
if there is only one Performer for a Performance (1:m relation). Could
also be you need a table, which contains the Performers-ID and the
Performance_ID together: More than one Performer for a Performance, also
moere than one Performance for one Performer possible (n:m relation)
Table 4 - Location
ID
Studio
Concert - open air
Concert - Hall
How should this table be linked to the other tables?
Calculations and reports won't be a problem. But the most important
problem is to create the right tables. Content in one table shouldn't be
reported too much. But the best start will be one table with all the
content to see which content will be repeated in the table. Then you
could split the repeated content from the table and set a foreignkey to
another table with this content instead.
Regards
Robert
--
Homepage: https://www.familiegrosskopf.de/robert
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy
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.