Calculated Field

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I understand that calculated fields should be used in forms/queries, not in
tables.

My scenario is this.
Table 1
Model
Serial
Total Flight Hrs.
Table 2
Flight
Model
Serial
FlightHrs
etc....
Form
FlightNo
Date
Model
Serial
Hours
CumulativeFlightHrs (using dlookup for TotalFlightHrs + Hours from form)

I want to always be able to know the cumulative flight hours and have it
always associated with the model for exporting, etc. Is this ok, or is it
better to not have the field in my table 1?
 
I forgot to add that some of the total flight hours were initially entered
from another database and cannot be calculated...the reason why I thought I
should maintain the field and just recaclulate after each flight.
 
Trying to understand what you have. Table 1 is the base information. Table
2 are transactions. You could make the initial flight hours an initial
transaction or a in another table and then use a query to get the sum of the
hours and just update in the form after you have entered the current flights
information. I was always taught that a good database stores nothing it can
calculate.
 
Back
Top