View Single Post
  #1  
Old January 5th, 2010, 09:04 PM posted to microsoft.public.access.tablesdbdesign
icccapital
external usenet poster
 
Posts: 88
Default Design theory for maintaining historical address communications

I was curious to get some ideas for the best way to maintain the address of
mailers that had been sent out.

So by way of example we send out mailers or invoices periodically. And lets
say they go to Joe Smith at 1 place last quarter. Now when Joe Smith changes
his address we then send it to 2 Other Place. Originally I had designed the
database to have the linking table with the invoice number and the client
contact ID, but the issue with that is that when Joe Smith changes his
address it appears that we sent the invoice last quarter to the new address.

Theoretically, what do you guys think is the best way to manage this. I
could copy the address into the linking table and get rid of the contact ID.
Or create a new contact id and copy the address and person into a new table
that basically represents that period's address information. So Joe Smith
would be in this table twice, once with old address with the last quarter
date and once with new address and this quarter's date and the linking table
would point to the ID for these. What do you think?