To Homework

IT 240 -- Final Project - Part II

Midwest Sports League Database (final version)

Final-part1.htm described Part I of the Final Project, this document describes Part II.
Please read carefully.

This is your final project and the final version of the Midwest League database. Make this your best effort because I'm going to look at all requirements much more closely than I have on previous versions of your database. The requirements include all of those from Final-part1 plus a final expansion, as described below. I will be grading on both functionality (do the forms and reports do what they're supposed to do) and design (see Form and Report Design below).

The Final Expansion of the Database

The first thing that you'll need to do is to modify the relationships to accommodate the many-to-many relationship that exists between sponsors and teams. One sponsor can support many teams, and one team can have more than one sponsor. We've dealt with a number of situations like this in the past, see, for example our 240class-v3.mdb (Students <--> Sports) or in our HenryBooks.mdb, where the Wrote table was a bridge between the Author and Book tables. You also dealt with this in part 1 of the Midterm (remember the Comptopia database?). Review how we resolved the many-to-many relationships in those databases, then use the same technique to resolve the many-to-many relationship that exists between the Sponsors table and the Teams table (you will need to create a bridge table). Here is the sponsorship information that you'll need: S01 sponsors teams T01 and T06; S02 sponsors teams T02, T03, and T07; S03 sponsors team T03; S04 sponsors teams T04, T06, and T07; S05 sponsors teams T02 and T04; S07 sponsors teams T01 and T03; S09 sponsors teams T04, T06, and T08. Establish all necessary relationships.

Using all fields from the Sponsors table, create a Sponsors form. It should have the same look as the Players, Coaches, and Teams forms (headings, text fields, command buttons, etc.). And like those forms, the Sponsors form is primarily for entering new sponsors.

Delete your existing Relationships report, then create a new report based on the new relationships.

Modify the Teams form to contain a third subform, namely the Sponsors Subform. But before you can do that modification you will have to create the Sponsors Subform. One way to do this is to use the Form Wizard to create a form/subform, choosing the Team table for the main form and Sponsors table as the subform. When the wizard finishes you will have a Sponsors Subform created. Since you already have a Teams form, the wizard will have created another teams form called Teams1. You don't need it, so just delete the Teams1 form. Next you need to get your Sponsors Subform onto your Teams form. Open your Teams form in design view. Make it small enough so you can also see the database window.  Make some room on the Teams form to accommodate the Sponsors Subform. Now click, drag, and drop the Sponsors Subform from the database window onto your Teams form. Reposition. align, and size everything so the form looks good. Of course, check it all out to make sure all controls work properly.  Here is a screen shot of the new Team Form (after clicking, click on the image of the form to enlarge it).

Modify the main switchboard to include an option to display the Sponsors form.

Form and Report Design

1. Same overall design
   • Same heading style
   • Same grouping technique
   • Same special effects
   • Same color scheme
   • Same font type
   • Same font size
2. Good alignment and sizing of all controls
3. Similar controls in same place on all forms
4. Related controls are grouped together
5. All items are properly centered
6. Combo box fields are used when appropriate
7. Proper labels attached to controls
8. If you used a logo, is it used consistently throughout?
   Is it the same size and used in the same place on all forms/reports?
9. If the form/report were printed, would all items print on one page
10. All items display properly. Keep scrolling to a minimum
11. Are all your text boxes and labels easy to read? In this regard, be careful about choosing
    foreground/background colors, e.g., don't choose a dark foreground on a dark background.
12. For readability, have you created captions for your field names?

When I'm grading your Final Project, I will be going over this list and deducting points for lack of good design.

Final Project Submission

• After you're sure everything is okay and just before you submit your database, pull down the Tools menu, click the
  Database Utilities command, and Compact and Repair Database.
• Your database file must be called FP-Smith.mdb, where Smith is your last name.
  Submit your FP-Smith.mdb file using COLweb.

• This is the end - nothing more. Thank you for all your effort in completing this course. Hope you enjoyed it and learned some useful stuff about databases. And good luck in your future endevors.