Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
To use calculated field or not?
Message
 
 
À
Tous
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
To use calculated field or not?
Versions des environnements
Visual FoxPro:
VFP 9 SP1
Divers
Thread ID:
01532936
Message ID:
01532936
Vues:
144
Hi,

I am looking for suggestions of better practice when using or not using a Calculated field. Let me describe on an example what I mean by Calculated field (perhaps this is not quite the right term).

Purchase Order and Invoice System. There is a P.O. table (vendor, date, amount, etc.). and P.O. Invoice table. Invoice table is a child table where there could be several records for each P.O. Each P.O. Invoice record has Freight and Sales Tax amount. I need to show on the P.O. Master view the total amount of Freight and Sales tax paid against the P.O. So one approach is to add fields FREIGHT and SALES_TAX to the P.O. Master table and update it on every entry in the Invoice posting. Another approach is to NOT to have these fields in the P.O. Master table but to calculate the total amount on-the-fly. That is, call a method/function that gets all invoices of the P.O. and calculates the total amounts.

Which of the two approaches is better practice, in your opinion. TIA.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform