Using multiples instances of a table in a relation scheme

S

Stephane

We have create a global database for the company that does CRM, quote,
orders, samples etc
The resulting relationship scheme is hard to visualize as there is many many
relations. I'd like to
create visual "clusters" on the screen to make it easier. Is it a bad idea
to re-use the same table
(but with different aliasto make relations easier to read on the screen?

for example instead of using

Customers <> Orders
Customers <> Samples
Customers <> Quotes
Customers <> Projects
Customers <> Contacts

do the following

Customers alias "Customers_1" <> Orders
Customers alias "Customers_2" <> Samples
Customers alias "Customers_3" <> Quotes
Customers alias "Customers_4" <> Projects
Customers alias "Customers_5" <> Contacts

then the "relation lines" are within a same group, easier to read then the
web of relation I have
right now

Thx
Stephane
 
J

John Vinson

I'd like to
create visual "clusters" on the screen to make it easier. Is it a bad idea
to re-use the same table
(but with different aliasto make relations easier to read on the screen?

I don't think that should cause any harm. Access itself will create
alias icons when you have multiple relationships between tables. Just
add the table to the relationships window twice or as many times as
need be.

Note that the relationships window has ALWAYS been a bit buggy and
unreliable - relationships and table icons may disappear or move
around for no apparent reason.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top