|
I made a post yesterday here. After many hours, a severe headache, and some tylenol I have decided to try and see if I can get some help on this many-to-many relationship that I was suggested to try and use. I decided to define my tables a little better to hopefully provide you guys with some more and clearer information. Here is a screenshot:
How can I accomplish this with either a one-to-many or a many-to-many relationship table? Thanks!
(comments are locked)
|
|
Something like this what you are after? @SirSQL on line 3, 4, and 5 you have "c.Aset AS Asset" etc... What exactly are you doing with this? It looks like you are declaring variables almost but I'm not sure if I am even on the right path.
Sep 07 '12 at 04:56 PM
jordanw44
I see definite benefits in re-organizing my database like this. I would have to change a couple things around in one of my programs insert statments but this could be tremendously better in the end. I can see myself needing to know what computers are mapped to each printer as well so I will study up on my pivot's.
Sep 07 '12 at 05:50 PM
jordanw44
(comments are locked)
|
|
No, something like this: Then you only put computer information into the computer table. You only put printer information into the printer table. The relationship table defines if it's a default wristband, hoozymawatchit or anything else. Then, the ComputerPrinter table brings them all together. This way you can get listings any way you want them. I will tell you, the one wrinkle is, if you want to output printers across the page for each computer, you'll need to use a type of query called a pivot. I leave that to you for additional homework.
(comments are locked)
|



