Thanks for the advice! I'll see if I can make it work with what we have going.

Still not sure if I answered your question. What I need is a handy list showing all the events at a location so I can quickly see the history of the location and be able to reference all the activity associated with it.

Hi Phil, thanks for responding. This database doesn't contain any of the climate data. That's somewhere else. The database essentially has 3 main tables:
1) Location: this is a tree that has a logger mounted on it. The location ID is the primary key and then there's UTMs, elevations, forest type, etc.
2)Logger: The logger ID is the primary key. Other fields include serial number, logger type, notes.
3)Logger event: This table tracks...

Hello!
I'm trying to reorganize an old database that has gone through many handlers over the years. I would like to relate 2 tables: Location and Logger_Events. We collect climate data and the loggers are unreliable and are frequently being replaced or moved between locations. For this reason, it is helpful to have 2 fields in the Logger_Events table called Old_location and New_location that show where a logger is coming from and going to....