J
John Vinson
It's considered polite to ask questions in the text area (the big
white box), not just the subject line.
As for creating a number field in a table that "counts up" - you
probably DON'T.
Storing derived data such as this in your table accomplishes
three things: it wastes disk space; it wastes time (almost
any calculation will be MUCH faster than a disk fetch); and
most importantly, it risks data corruption. If one of the
underlying fields is subsequently edited, you will have data
in your table WHICH IS WRONG, and no automatic way to detect
that fact.
Just redo the calculation whenever you need it, either as a
calculated field in a Query or just as you're now doing it -
in the control source of a Form or a Report textbox.
Just use a Totals query.
If I've misunderstood your question, please post back with more
details.
John W. Vinson[MVP]
white box), not just the subject line.
As for creating a number field in a table that "counts up" - you
probably DON'T.
Storing derived data such as this in your table accomplishes
three things: it wastes disk space; it wastes time (almost
any calculation will be MUCH faster than a disk fetch); and
most importantly, it risks data corruption. If one of the
underlying fields is subsequently edited, you will have data
in your table WHICH IS WRONG, and no automatic way to detect
that fact.
Just redo the calculation whenever you need it, either as a
calculated field in a Query or just as you're now doing it -
in the control source of a Form or a Report textbox.
Just use a Totals query.
If I've misunderstood your question, please post back with more
details.
John W. Vinson[MVP]