Sabtu, 02 Mei 2015

Re: [MS_AccessPros] Design question

 

Jan

A junction table connecting candidates to  contacts would be a simpler solution in my opinion. 

Glenn


Sent from my Samsung Galaxy Note ll Mobile  

-------- Original message --------
From: "jan.hertzsch@gmail.com [MS_Access_Professionals]"
Date:2015-05-02 6:11 PM (GMT-05:00)
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Design question

 

I needed to keep the sets of contact records separate for two "clients".  Think of it as the contact lists of two candidates in the same 3 precincts. I knew I was doubling my work when this started but I kept them as two databases at the start.  As you might imagine, I have a fair population of contacts (voters, donors, volunteers) who are common to both so I now want to create a single database but I still have to be able to process Candidate A contacts from Candidate B contacts. 


I already keep a field called "Tags" in each of the Contact_table(s). My plan is to simply add a tag for Candidate_A and one for Candidate_B. When I merge the two Contact_Table(s), I will add the appropriate tags.  I am trying to think this through but I THINK it will allow me to only extract Candidate_A's conacts.


For example, I envision a query that

includes

  •  Candidate_A,
  • Donors,
  • Volunteers

but excludes

  • Deceased, and
  • Moved records.

Good design? Bad design?  Thoughts?

__._,_.___

Posted by: Glenn Lloyd <argeedblu@gmail.com>
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (2)

.

__,_._,___

Tidak ada komentar:

Posting Komentar