Jim -
You will need a Management_Assoc table that has a foreign key to each. Think of it as a customer/product relationship. A customer can order many products. A product can be ordered by many customers. Presto! A Orders table showing who ordered what.
Same thing with your many-to-many situation.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
https://mvp.support.microsoft.com/profile/Bill.Mosca
--- In MS_Access_Professionals@yahoogroups.com, "luvmymelody" <luvmymelody@...> wrote:
>
> Hello all,
>
> After building the database for my client and a year of use we discovered that some information was not conveyed to me before I designed the database. The database tracks Management companies with the Home Associations related to the management companies. So I have a one to many for One Management company to many Associations. But I found out that an Association can change management companies at will.
> Right now I have tblManagement in a one to many with tblAssociation linked on ManagementCoID in both tables with a one to one relation to tblProjects linked on AssociationID in both tables.
>
> I know that I had set up primary keys for the tables yet somehow they are gone and the duplicates are set to ok for dups. Now we have multiple Associations in the table. I need some help.
>
> How would I go about creating a many to many for the associations and management co tables?
>
> Thank You
>
> Jim Wagner
>
Tidak ada komentar:
Posting Komentar