There is a way around it but it isn't very pretty.  You can store the
history of address / detail changes with start and end dates, then compare
the transaction date to find which address was valid at the time of any
given transaction.  This uses less data than storing the address with each
transaction, but makes retrieval slower and it less "obvious" how to get
thet data you need.


-----Original Message-----
From: Haslett, Andrew [mailto:andrew.haslett@i...]
Sent: Thursday, November 28, 2002 9:55 PM
To: Access
Subject: [access] RE: Transaction History


Why does it matter if sender or beneficiaries details change?

Is it important than an old transaction retain (be linked to) those details
AT THAT TIME?

If it is, then there's no way around storing their details with every
transaction.

If not, then it won't matter storing their details once in the senders and
beneficiaries table.

Think of it this way:
If you are producing a report listing all transactions, do you want to show
the sender and beneficiaries details for EVERY transaction, as they were at
the time of the transaction.. or only once, as they are now...

Cheers,
A

-----Original Message-----
From: Enzo Zaragoza [mailto:enzaux@g...]
Sent: Friday, 29 November 2002 1:10 PM
To: Access
Subject: [access] Transaction History



	Hello!!!  I would like to have your opinions on my query.  Here is
my situation:

      I'm doing a remittance system.  I want to know what's the best way my
transaction table
be set up.  I have a Transaction table (tblTranx), Sender Table (tblSender)
and Benificiaries'
table (tblBene).

tblTranx             tblSender        tblBene
------------------------------------------------
TranxID
SenderID     M--1   SenderID    1--M  SenderID 
BeneID                                BeneID
   ^M----------------------------------1^

	A transaction contains the following:
1.) Sender & Beneficiary
     - name
     - address
     - tel no
     - cell no
     - other infos

2.) Amount to be remitted
3.) Other Infos

	What I'm concerned with is the Sender and Bene part.  What I want
know is which is better
to do with the Sender and Bene info, to have only tblTranx.SenderID be
linked only to 
tblSender.SenderID or to create fields in tblTranx for Sender and Bene Infos
such as name, addr, etc ?  
Taking into considerations that if the Sender and Bene have changes in their
info in the near future.

	Currently what I'm doing right now is the second option (created
fields in tblTranx for Sender
and Bene Info) because if the sender or bene changes any of its information
at least the past transactions
would not be affected since tblTranx has fields that stored the info.

	Am I doing the right way?  Or are there any better options than
these?  Because with the option I use,
bloated database is all I have because repeated infos are stored on
tblTranx.  Any tips and suggestions?

Thanks,


Enzo c",)
YahooID: yackydidakdak



IMPORTANT - PLEASE READ ******************** 
This email and any files transmitted with it are confidential and may 
contain information protected by law from disclosure. 
If you have received this message in error, please notify the sender 
immediately and delete this email from your system. 
No warranty is given that this email or files, if attached to this 
email, are free from computer viruses or other defects. They 
are provided on the basis the user assumes all responsibility for 
loss, damage or consequence resulting directly or indirectly from 
their use, whether caused by the negligence of the sender or not.