Database design and reporting with LOTS of fields
This is not, I fear, a simple question.
Here’s the situation: I’m a birdwatcher and like many birdwatchers, try to keep good notes about what I’ve seen. To help me on a recent trip to Australia, I created an FM11 database (see the screenshot). To account for the possible 643 species of birds I might see on a given day, I had to create 643 number fields, then 643 summary fields to count the total number of a particular species I’d seen by the end of the trip.
Needless to say, this took a while. It’s also proved beyond my modest capabilities to create a printable daily report that would list just those species I saw that day, not all 643 possibilities. Can anyone suggest how I might do that? Is my approach wrong? Thanks in advance.