Elpidio Latorilla wrote:
I propose we create a new table called "care_transaction" with following fields:A single date to indicate timestamp when transaction is inserted may suffice instead of having date_start and date_end.
nr = primary key (unique, autoincrement)
code = the transaction code (the actual flag)
product = eventual product identifier
encounter_nr = the encounter number of the transaction (foreign key)
date_start = the start date of the transaction
date_end = the end date of the transaction
count = the multiplier of the transaction
You may want to also include a status flag(s) for indicating whether the transaction has been billed, cancelled, served, etc.
Prices of certain items could change from the time it was inserted into the transaction table and the time it is billed for payment. This complicates things and you may want to leave it for the time being. Otherwise, a price field (and discount field) needs to be added as well.
Best regards.
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
