Deadline getting closer - still stuck in table design phase

ST4RCUTTER

Registered User.
Local time
Today, 06:05
Joined
Aug 31, 2006
Messages
94
Thanks to all who have provided help on other threads. I have made some progress but I am still struggling with the last couple of relationships here. I am tracking projects and have normalized this data into the following tables:

tbl_customers (contains customer specific information)

  • Is on the "one" side of a 1:many relationship to tbl_workorders. (1 customer for multiple WO's)
  • Is on the "one" side of a 1:many relationship to tbl_locations (up to 2 locations per customer).
  • Is on the "one" side of a 1:many relationship to tbl_circuits (up to x number of circuit ID's for each customer)

tbl_workorders (contains order specific information)

  • Is on the "one" side of a 1:many relationship to tbl_costs (multiple costs for each WO).
  • Is on the "one" side of a 1:1 relationship to tbl_services (each WO can only have one row on the services table. I suppose I could combine all fields onto 1 table, but logically they represent different information. The WO table is about the work order and the other table deals with the customer's services.)
  • Is on the "one" side of a 1:many relationship to tbl_contacts (can be multiple internal contacts for each WO)


tbl_dates (contains as many as 33 possible dates for each project)

This table is one that I am having trouble with. Each work order can have any of the possible dates on tbl_dates. I have designed tbl_dates to be as normalized as possible. You select a date type and enter the date. I can't figure out where to relate this to tbl_workorders without using the WO field. Perhaps I am designing this table incorrectly.

Any help is appreciated. Thanks!
 
So when's the deadline?

Do you think anyone will help? :D

Oh, by the way, it's nice to see you're still alive and kicking. :)
 

Users who are viewing this thread

Back
Top Bottom