|If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.|
||Thread Tools||Display Modes|
Beginner - 3 tables in 3 loops
Thanks for explaining that... now if I could just the OP to explain more
we'd be set!
2010 Microsoft MVP (Access)
"I feel I have been denied critical, need to know, information!" - Tremors
"Fred" wrote in message
More from my EE background than my (much less than yours) database
background, I think that the generators are handled as one-of-a-kind items,
not a list of types that would get used multiple times. Each
instance/installation of a "generator" is typically a $xxx,xxx,xxx.xx
multi-year construction project. If so, then "Generator #1" is just half
of the name given to a particular generator. The full name might be Plant
#5-generator #1 If that were true, IMHO a junction table would not be
- - -
In order to have a good database, or to explain enough to us to help, you
are going to have to start with deciding upon what the entities are that you
are going to database, and what the mission that you want it to accomplish
is. Do this without using any database terminology.
IF (and I emphasize IF, because we don't know that) you main mission were to
track and completed maintenance, then instance of required-then-completed
maintenance would be your main table. In that case the year and or date
would be merely a field, If my guess address to Gina were right, you
would probably have a table with listings of your individual generators.
plant # might be just half of the name of that generator, or an attribute of
Again, these are just guesses. You'll have to tell us more to get a real
Hope that helps a little.