Hi
First of all, setting up relationships is one of the many common steps
involved in designing a relational database system. Let's back up a little
and throw in another step that's just as common in designing a relational
database system, and that is Normalizing tables. Normalizing tables is
essentially the process of breaking up a whole slew of related information
into more efficient, distinct, manageable, units. Once we achieve
normalization, since our "slew of information" is now broken up into units
we need to define how the distinct units are related to one another so that
the database management system (i.e. Access) can reproduce this "slew of
information" intact.
So, why setup relationships between tables? Because the tables had been
normalized. The less normalized your tables are, the less you need to setup
relationships. As a matter of fact, just about all database application can
be done with one table. That's right! With one huuuuge table, I guarantee in
this case that you dont ever need to setup relationship <g>.
To answer your question though (what do we gain by setting up
relationships).
Well, we dont gain anything from setting up relationships, at least not
directly. We do, however, reap the benefits of data integrity, efficiency,
reliability from normalization of tables which, in turn, requires
relationships to be setup.
HTH
Immanuel Sibero
