Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cbolwerk
Starting Member
1 Post |
 Posted - 2008-10-11 : 13:11:46
|
| I have 3 tables (for now) that I am trying to figure out how to relate them properly. This application is in a manufacturing environment. The tables that I am starting with are Area, Line, and Equipment, listed in order of general to specific. I have the relationship for Area and Line (one-to-many), but am having difficulty with Equipment. I don't think that I can just do a relationship between Equipment and Line because there could be equipment with similar names but on different lines and/or in different areas.Or, am I looking at this all wrong? Should I have a table with equipment names, line names, and area names, and then a table that joins them all together? I am thinking that would keep redundant data to a minimum.Eventually I am going to add a table that will be called Issues. My intent is to create an Issues database and allow people to select the area, line, and equipment, and then enter some info on a problem. I am also going to be using VB 2008 as the front-end. I mention this because I am wondering if one way is going to be easier for creating the Windows forms.Thanks for any help!!! |
|
|
Rob555
Starting Member
5 Posts |
Posted - 2008-10-12 : 12:32:57
|
| If you're going to be tracking issues, shouldn't your equipment have a unique ID and/or name?For example, if I have a fleet of vehicles I may have 20 Toyota Camrys, but I could use the VIN or some other assigned number to track repairs and assigned driver. |
 |
|
|
countryjimbo
Starting Member
1 Post |
Posted - 2008-10-30 : 07:41:59
|
| I think you should have seperate tables for Equipment, Lines and Area with each record having unique ids. Then have another table that links Equipment to lines and areas, use the ids to reduce redundancy. |
|
|
|
|
|
|
|
|
Table design question