Same field-many relationships

  • Thread starter Thread starter baraka
  • Start date Start date
B

baraka

I am posting this with the very hope that a Microsoft MVP would recommend
something very useful so that I don't have problems with my database in the
future.

Here is my problem:

My tables have a peculiar relationship, almost all of my other tables are
related to two tables in a one-to-many relationship. The design therefore
forces me to create the relationships with
the same field having multiple relationships to several similar fields in
many tables.

My problem is, Is it good practice to relate my tables as such? If not, is
there another way to rearrange the relationships so that I don't have design
problems in the future? The reason why I am asking this is because this same
design is what I think is giving me problems continuing with my database
design and I have decided to start all over again but this time I want to
make sure I don't make any initial false steps.

Any help would be highly appreciated.
 
It is difficult to describe the situation that is why I attached a diagram
to my previous post "Help Required with Table Relationships". But some
people complain that it is not good netiquette. Please who ever wishes to
help me, let them open that post. The attached document is only a diagram
and not a virus.

while looking forward to some immediate help, I remain,

yours truly
Baraka.
 
You are unlikely to find many takers -- and the newsgroup restriction
against attachments is both to reduce the possibility of virus, but also
because some newsgroup readers pay by the minute for their connection. Any
post with an attachment requires minutes of download, so they have a(nother)
dis-incentive to even look.

Your description could be as simple as:
A table with Orders, including date, person ordering, and person taking the order; and
A table with OrderDetail, including OrderID, ItemID, Quantity, and
Click to expand...
SalesPrice.

This much of an explanation would give readers a context.

Good luck

Jeff Boyce
<Access MVP>

P.S. Your assurances notwithstanding, there's little incentive to risk a
virus.
 
I have a table named VehicleBasicInfo which has an ID field which has a
one-many relationship with similar fields to four tables, eg accidents,
fuelUsage, maintenance etc.

what I want to know is if it is good design practice to connect a single
field (here the ID field) to many such similar field in many tables such
that in the relationships window you see the ID field connected to may
tables with lines.
 
Back
Top