Database relationships (1 Viewer)

The Archn00b

Registered User.
Local time
Today, 12:07
Joined
Jun 26, 2013
Messages
76
This might seem like a stupid question, but is the general rule for a relationships between fields (one to many specifically) only one relationship per pair of fields? Will it cause problems if you have a field linked to two fields each through a one to many relationship? Thanks!
 

plog

Banishment Pending
Local time
Today, 14:07
Joined
May 11, 2011
Messages
11,638
Gonna need a more concrete example. I can't really understand the number of relationships and fields you want to use. Use these tables:

TableA
Field1, Field2, Field3, Field4

TableB
Field5, Field6, Field7, Field8

Relationship1 =
Relationship2 =

Fill in the relationship info.
 

ButtonMoon

Registered User.
Local time
Today, 20:07
Joined
Jun 4, 2012
Messages
304
This might seem like a stupid question, but is the general rule for a relationships between fields (one to many specifically) only one relationship per pair of fields? Will it cause problems if you have a field linked to two fields each through a one to many relationship? Thanks!

No. It's quite common to have attributes subject to several different relationships or to have multiple relationships between the same two entities.

Unfortunately the "relationships" window in Access makes an awful mess of displaying models of that kind. It insists on displaying a copy "shadow" table whenever a table is referenced more than once. If you intend to spend a lot of time on modelling or if you want to produce an ER diagram for sharing with others then use a decent third-party tool rather than try to rely on Access.
 

The Archn00b

Registered User.
Local time
Today, 12:07
Joined
Jun 26, 2013
Messages
76
Like:

Table A Field1 has a one to many relationship with Table B field6
Table A Field1 also has a one to many relationship with Table C field10
 

ButtonMoon

Registered User.
Local time
Today, 20:07
Joined
Jun 4, 2012
Messages
304
Table A Field1 has a one to many relationship with Table B field6
Table A Field1 also has a one to many relationship with Table C field10

Nothing wrong with that. What matters is that you apply some sound principles in your design process: identifying the business rules, keys, datatypes, Normal Form, and so on.
 

The Archn00b

Registered User.
Local time
Today, 12:07
Joined
Jun 26, 2013
Messages
76
Nothing wrong with that. What matters is that you apply some sound principles in your design process: identifying the business rules, keys, datatypes, Normal Form, and so on.

Thanks for the advice ButtonMoon. I appreciate it!
 

Users who are viewing this thread

Top Bottom