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

I do have an invoices table, are you thinking that there should be the
address for each invoice created or if thre are two addresses a secondary
table that would have invoice id and the address so it is kept like that?
And each period addresses are written to this table as invoices are created?

I was trying to clarify what you said to see if i understood. thanks

"Fred" wrote:

IMHO you have a fundamental "entity: issue. The invoice, with all of it's
then-current details, is an entity that you created and need to look back at.
In that case you would probable need an "invoices" table (probably a pair of
linked tables, the header information and the detail information.