help with table design/db structure

[william.jackson]

Hello...

This is my situation...

I am trying to develop an Access DB to capture observations where there
are multiple observers that will observer for a 15 min interval for a
total of 13 intervals. I hope you were able to follow me. I'm stuck
with trying to relate/structure my DB to cycle/auto populate the DB for
each interval administrated by the observer. I thinking this would be
in a separate table for the main table that captures certain info about
the observer, etc - there is an observation code in that table. I'm
thinking that the observation code and interval need to be tied
together as a dual primary key or something of the sort.

 

[TC]

What about this:

tblObserver
ObserverID < primary key
observer's name, contact #, etc.

tblObservation
ObservationID < primary key
ObserverID
ObservationDate (date/time)
Value1, Value2, etc.

Each observer (person) has a record in tblObserver to hold their
personal details.

Each observation has a record in tblObservation, containing the
observer's ID, the date & time of the observation, an the actual
observed values.

HTH,
TC [MVP Access]

 

[Duane Hookom]

I don't have a clear view of the requirements but I would not store multiple
observation values in a single record.

Start with a single observation and then group like observations. The common
attributes of the group belong in a related parent record. Then group like
parent records to find common attributes that belong to the grandparent
record.

 

[TC]

Yes, good point.

If the OP reponds, we can observe what he says!

Cheers,
TC [MVP Access]

 

[TC]

Yes, good point.

If the OP responds, we can observe what he says!

Cheers,
TC [MVP Access]