Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Database Design

Status
Not open for further replies.

ccnetwork

Technical User
Feb 5, 2007
12
GB
Hello

I'm creating a database that will contain information on committee events. Each committee will contain the following information.

Committee Name (Text)
Committtee Date (Date)
Pre Agenda Date (Date)
Manager Deadline (Date)
Draft Deadline (Date)
Final Deadline (Date)

I am looking for the best way to contain the above information in my database as I'll need to produce monthly calendar type reports in Crystal as like the attached screen shot.

I know for a fact I'll have a table that lists all committees. However I don't know the best way to store the other information.

The attached screen shot is based on the following information being stored in the database.

Committe Name: Committee A
Committee Date: 26/02/2008
PreAgenda Date 10/02/2008
Manager Deadline:1302/2008
Draft Deadline: 17/02/2008
Final Deadline: 21/02/2008


Please let me know if you require anymore information about the database and I will gladly provide.

All help is greatly appreciated
 
I would make sure the database is normalized. I would have tables for:
tblCommittees (one record per committee)
tblDateTypes (one record per type of meeting)
tblSchedule (one record per committee per meeting)

With 5 different date types, I would not create fields with names like "PreAgendaDate" and "DraftDeadline". These should be values stored in fields, not in field names.

There is a sample of a calendar report at Calendar Reports sample

Duane MS Access MVP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top