B
bw
I have a table in use, that I am restricting to one record, which is used as
the total number of items (call them apples), to be considered for
calculations elsewhere on Forms and Reports. I guess this is looked at as
an unbound field that remains constant for all calculations, until the value
in the table changes (infrequently).
So CURRENTLY, the table consists of AppleKey (autonumber field, Validation
Rule = 1), and TotalNumApples (number field).
I'd like to change the table so that it ALSO acts as a history file. The
table would include the number of Apples added, and the date the Apples were
added (but not necessarily the total of all Apples added).
The PROPOSED table would consist of AppleKey (autonumber field),
NumApplesAdded (number field), DateAdded (date field)
So my question is, how would I use this new table to:
Calculate the total number of Apples in the table for a report (and store
it where?).
Use this total number of Apples added as my unbound field for calculations
as I currently do.
Thanks,
Bernie
the total number of items (call them apples), to be considered for
calculations elsewhere on Forms and Reports. I guess this is looked at as
an unbound field that remains constant for all calculations, until the value
in the table changes (infrequently).
So CURRENTLY, the table consists of AppleKey (autonumber field, Validation
Rule = 1), and TotalNumApples (number field).
I'd like to change the table so that it ALSO acts as a history file. The
table would include the number of Apples added, and the date the Apples were
added (but not necessarily the total of all Apples added).
The PROPOSED table would consist of AppleKey (autonumber field),
NumApplesAdded (number field), DateAdded (date field)
So my question is, how would I use this new table to:
Calculate the total number of Apples in the table for a report (and store
it where?).
Use this total number of Apples added as my unbound field for calculations
as I currently do.
Thanks,
Bernie