A family of Microsoft relational database management systems designed for ease of use.
Each Person may have zero, one or many Visits: a one-to-many relationship from Persons to Visits on PersonID.
Each Facility may be the site of zero, one or many Visits: a one-to-many relationship from Facilities to Visits on FacilityID.
You seem OBSESSED with the idea that you must have "a series of N tables". YOU DO NOT NEED N TABLES and I don't understand why you feel that you do! At the VERY most, you might have N tables, temporarily, just to migrate your data, but in the production database you will need one and only one Visits table with many records, for many persons, for many facilities. I don't know where you're getting your data (on spreadsheets from an external source perhaps?) but what you will need to do is import or link to the exteral source and run one - or many - Append queries, appending a VisitID, a FacilityID, and a Visits number value from each record in your source table into a new record in the normalized tall-thin Visits table. When you want to generate a Report you would create a new, three-table query joining Visits PersonID to Persons.PersonID, and Visits.FacilityID to Facilities.FacilityID. In that query you can then select the name of the person from Persons, the name of the facility from Facilities, and the number field from Visits; you can group by, sum, average, count, crosstab this query however you like.