P
Pamela
I created a db and in reading now about db structure, I've seen a lot of
mention of relationships. My db started out very simple with the tables that
I used for relationships all being one-to-one and now I'm considering adding
to it. In it, however, I also have some tables that I used (not w/ the
Lookup Wizard but on my own) simply as lookup - populating cbos. I didn't
seem to need to set relationships with these though for it to work and work
well. Why didn't it require a relationship and what are the pros & cons of
setting them up this way vs. w/ a relationship?
Thanks so much for your help!
Pamela
mention of relationships. My db started out very simple with the tables that
I used for relationships all being one-to-one and now I'm considering adding
to it. In it, however, I also have some tables that I used (not w/ the
Lookup Wizard but on my own) simply as lookup - populating cbos. I didn't
seem to need to set relationships with these though for it to work and work
well. Why didn't it require a relationship and what are the pros & cons of
setting them up this way vs. w/ a relationship?
Thanks so much for your help!
Pamela