Retaining old info

  • Thread starter Thread starter Colin Foster
  • Start date Start date
C

Colin Foster

Hi Group,
I just want to clarify my understanding on this one...
I have as part of my database a client record with his address; if he
changes address then I want to make sure that his latest address is the one
shown now & onwards, however, if I understand things correctly, when I
change his address, if I look at an old record that used this client before
the address change, then the old address would be replaced by the new one.
If I wanted to see the old address instead, then I would either have to give
the option of alternatives, or create a new record for the client with the
new address... or is there another way???
It's not a problem, as such, I just want to get my head around things!
Regards
Colin Foster
 
I'm assuming that you have a Client table (tblClient) and a Client
Transaction table (tblTransaction), and that you have a relationship set up
between ClientID (the primary key from tblClient) and a corresponding foreign
key field in tblTransactions. In that case every record in tblTransactions,
old or new, will show the current information from tblClient. One
possibility is that you could store the actual client information such as
address (rather than just the PK field) in tblTransactions. Without knowing
how your database is set up it is difficult to be specific about how this
would be done.
Another possibility would be to have an address table apart from the client
table, and to establish a relationship between ClientID from tblClient and a
corresponding foreign key in tblClientAddress. Each address entry could be
dated (for instance, after a change of address a new address record would be
generated with the current date, and the date of the transaction would
determine which client address would be used. Again, without details it is
difficult to be specific.
No doubt other possibilities exist, but these are the ones that occur to me.
 
Back
Top