Brad,
I had it really close to that, but not quite. Just to be sure, what would
you use for each relationship? or at least the junction table. I am using
the relationships feature.
I'm not sure what you're asking here.
Under the current setup, the relationships I have entered are:
Many Car #'s to one Trainset
One Car to CarTrain
One Train to CarTrain
Shouldn't there be more relationship hookup?
I dont know. Based on the requirements you set forth, no. We use tables and
relationships to model the real world. Generically, it's called relational
model or Entity Relationship model. Whether or not you need more tables
and/or relationships depends on the real world you're trying to model, and
only you know that world.
Based on the description of your post, this is what I'm getting:
A- You have Cars
B- You have TrainSet (although after more explanation from you, this is
more of groups of cars - we could have used CarSet)
C- You have Train
D- One TrainSet can have many Cars (1 to M). This relationship is
implemented by having TrainSetID as a foreign key in tblCar.
E- One car can be in many trains at different times, one train can have
many cars at one time. (M to M). This relationship is implemented in a
junction table tblCarTrain.
Points A, B, C above tells me you have 3 entities, points D, E tells me you
have 2 relationships.
So, should there be more relationships? Well depends, is there anything
else that I dont know about (i.e. I'm not getting from your description of
the problem)?
Immanuel Sibero