Binding a calculated check box

[emoffit8]

Is it possible to bind a check box whose control source is an equation to a
field in a table?? My check box determines whether or not an individual is
qualified at a certain level based on his score entered elsewhere on the form.
However, I want to represent all his qualifications in a report and thought
it would be best to attach them to his record. Is this even possible or do I
need to recalculate whether or not he's qualified in the actual report??
Thanks in advance.

 

[John Vinson]

Is it possible to bind a check box whose control source is an equation to a
field in a table?? My check box determines whether or not an individual is
qualified at a certain level based on his score entered elsewhere on the form.
However, I want to represent all his qualifications in a report and thought
it would be best to attach them to his record. Is this even possible or do I
need to recalculate whether or not he's qualified in the actual report??
Thanks in advance.

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 control.

John W. Vinson[MVP]

 

[emoffit8 via AccessMonster.com]

Thanks, John...figured that was the answer and reason.

Is it possible to bind a check box whose control source is an equation to a
field in a table?? My check box determines whether or not an individual is

[quoted text clipped - 3 lines]

need to recalculate whether or not he's qualified in the actual report??
Thanks in advance.

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 control.

John W. Vinson[MVP]