Amusement park database

[Mason]

Hi
I'm quite new to this and I could need some help, please. I'm trying to
create a database with information about fees and opening hours for different
amusement parks and zoological gardens. I want to search for instance
children fees in a special area or opening hours in that area. The problem is
that there is so many different fees involved some parks have free admittance
for everyone under 7 and one price for everyone else, some have many
different prices for adults, youths and family prices. The ages for a child
differs between the different parks. Then there is sometimes different fees
in the Sommer (high season).

The other problem is opening hours some have the same opening hours
monday-sunday while others have different opening hours during the weekends.
Any ideas how I should set up this?

Do I need to have a column for every age (0,1,2,3,4,5...67) and one for
every day of the week?

This is the data I have:
*Name of park
*Adress and other information
*Opening hours
*Fees

Hope I can get some ideas from you! Thank you. / Mason

 

[Jeff Boyce]

Mason

If you create a column "for every age", or a column for every amusement
park, or for every month, you have designed ... a spreadsheet! If you
insist on using this kind of design, you (and Access) will have to work a
lot harder than you need to.

Before you proceed any further, consider looking into relational database
(Access) design, and the topic of normalization. Take paper and pencil and
jot down the subject areas (e.g., person, park, ...) about which you want to
keep data. Then draw the lines (relationships) that connect these
"entities". Then start listing the specific data you'll want to keep,
within each subject area (e.g., you might want to keep firstname, lastname,
DOB about persons).

By the way, you are in the best position to decide ... you may want to keep
DateOfBirth rather than Age. If you are interested in the person-related
info, keep DOB and (re-)calculate Age. If you are interested in setting age
groups, you probably want to keep AgeGroup info.

Regards

Jeff Boyce
<Access MVP>