Relationships Between Tables

[nouveauricheinvestments]

I have two tables. One lists 7 different managers which are servers
that have been assigned numbers for simplicity and the other table,
which we shall call trades, references that managers table in a many
to one relationship. The field that looks up this information is
called manager ID. But it is not actually an ID. It is the server. I
don't understand what the point of showing a relationship is if it is
not changing anything. I mean, all I see it doing is giving me the
ability to easily go the managers table and see the trades in
subdatasheets divided by managers... Am I missing something??

If you can't tell, I am still learning access. I don't know if I fully
comprehend the concept of relational databases quite yet. Hence the
question.

 

[Keith Wilby]

I have two tables. One lists 7 different managers which are servers
that have been assigned numbers for simplicity and the other table,
which we shall call trades, references that managers table in a many
to one relationship. The field that looks up this information is
called manager ID. But it is not actually an ID. It is the server. I
don't understand what the point of showing a relationship is if it is
not changing anything. I mean, all I see it doing is giving me the
ability to easily go the managers table and see the trades in
subdatasheets divided by managers... Am I missing something??

I don't think so, no.

If you can't tell, I am still learning access. I don't know if I fully
comprehend the concept of relational databases quite yet. Hence the
question.

The point of a one-to-many relationship is that it enables you to present
the data to the user in forms and sub-forms in a logical manner. In your
case you'd have the "manager" data on the main form and "trades" data in a
subform, because each manager can have many trades. Does that help?

Keith.
www.keithwilby.co.uk