Jim
I'd set up an AssociationManagement table with a field Named Current (Yes/No).
That way if an HOA changes management companies you can keep the old record but unmark it as Current.
Are projects related to Management in any way? The HOAs I've dealt with use the Management to deal with the contracts, billing, etc. That would be handed over to the new Management so they are not really tied to the projects. Just to the HOA.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
My nothing-to-do-with-Access blog
http://wrmosca.wordpress.com
--- In MS_Access_Professionals@yahoogroups.com, "luvmymelody" <luvmymelody@...> wrote:
>
> Hello all,
>
> I am recreating a database that should have had a many to many relationship set up. There are 2 tables one with Management Companies and the other is the Home Owners Associations which are managed by the Management companies. A third table is called Projects where this table is linked to the Home Owners Association table, as there is 1 to many projects.
> The issue is that Home Owners Associations are now moving to and between Management companies. I have studied on how to define and set up the many to many relationships but I can not find out how to populate the junction table without manually adding the records.
>
> And how do the history of projects for associations not go away when the associations move to a new Management companies?
>
> So my question is how do I set up this many to many relationships?
>
>
> Thank You
>
> Jim Wagner
>
Tidak ada komentar:
Posting Komentar