ACCESS FEED: Re: [MS_AccessPros] Design question

Minggu, 03 Mei 2015

Re: [MS_AccessPros] Design question

Jan-

As long as the candidates aren't running against each other, I would do one set of tables and add a column to indicate the contact campaign source. If they are running against each other, then you must maintain separate tables!

John Viescas, Author

Microsoft Access 2010 Inside Out

Microsoft Access 2007 Inside Out

Microsoft Access 2003 Inside Out

Building Microsoft Access Applications

SQL Queries for Mere Mortals

http://www.viescas.com/

(Paris, France)

On May 3, 2015, at 12:11 AM, jan.hertzsch@gmail.com [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:

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