Attention Microsoft MVPs

[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.

 

[Jeff Boyce]

If you would provide a bit more information about the kinds of problems your
current database is having, the 'group might be able to offer suggestions
unrelated to your table structure.

Also, if you would provide an example of the kind of data you have related
in multiple one-to-many relationships, the 'group might be able to offer
pointers on the structure itself.

More info, please...

Jeff Boyce
<Access MVP>

 

[Cindy Winegarden]

Hi Baraka,

The number of tables you have related isn't important. What is important is
that your data is normalized and that each item of data is stored in the
appropriate table. As Jeff said, you haven't given any information about
that at all.