Hi PatAnd you didn't recognize this as inferior to the solution I suggested in #11?????
@robinfq the breakdown is more complicated than what was described. You could use a a table with 5 columns but I would probably use three related tables instead to avoid repetition and to give you the most flexibility.
tblEra
EraName (PK)
tblPeriod
PeriodName (PK)
EraName (FK)
tblEpoch
EpochName (PK)
PeriodName(FK)
StartYR
EndYR
You use tblEpoch for the criteria and then join up the line to get the other names.
Hi PatYour schema is incorrect. Look at the one I suggested in #19 again. The start and end need to go at the LOWEST level. While it is technically possible to use just the Start year or the End year for that matter, queries are far simpler if you have both start and end.
The relationship is Era, Period, Epoch and the years are associated with the Epoch which is the lowest level.
For this application, I would use the actual names rather than surrogate keys. It will be easier for the OP to understand and they are not likely to change but just in case, use Cascade Update on the relationship.
Not today. I have paying work to attend to.Are you able to create a form based on these tables?
Hi arnelgptry this sample also.
The point about normalisation is that you don't repeat derived data in a table.Hi y'all,
I am building a database of my fossil and geology collections. One thing that would be super useful would be for it to be able to auto-populate certain fields based on the data I enter in another.
For example: if I enter any figure between 66 to 145 in the 'Age (millions)' column, I would like it to automatically complete the 'Period' column to say Cretaceous, etc.
I am a complete beginner at Access so don't know if this is even possible but I feel like it should be. If so, please explain it like you would to your great gran as my knowledge on this is pretty basic!
Thanks