Let’s imagine that being the tech-savvy young go-getter you are you want to build a database to help you manage your club. First, you figure out what you need to store for your club called DEAD (Dedicated environmentalist activist drummers). For our purposes we'll assume you need to keep track of club members, volunteer events, fundraisers, and donor contacts. That tells you that you need four tables: Members, Events, Fundraisers, and Donors. Next you need to figure out how they’re related. Presumably every event and fundraiser is planned and managed by a member, so we know that events and fundraisers will have a relationship with members. Finally, we should decide what fields we need to create for each table. The Members table will be generated automatically by Access, so that’s taken care of. For Donors we'll store general contact information like first and last name, phone number, email, and mailing address. Events will have a name, the planned date, the date on which they took place, the cost, and the member who planned it. Fundraisers will have the same thing except they will also include revenue. It may be helpful to create a diagram of your database. For the DEAD database such a daigram would look something like this:

Now you can return your gaze to your monitor, bring your eyes into focus, and get started.