Totals from form not always picked up in table.

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

Guest

I track fmla leave in our office. I am using Access 2000. I have set up a
table and form to enter the information. On the form I have fields to enter
time used each quarter as well as a total field which adds the quarter
fields. In the table some of the records have the correct total and some
only have 0.

I do not understand why. Any ideas? Thank you.
 
I track fmla leave in our office. I am using Access 2000. I have set up a
table and form to enter the information. On the form I have fields to enter
time used each quarter as well as a total field which adds the quarter
fields. In the table some of the records have the correct total and some
only have 0.

I do not understand why. Any ideas? Thank you.
Click to expand...

I'm not sure how you're getting the total into the table in the first place -
but you *shouldn't be doing so*.

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.


John W. Vinson [MVP]
 
You should not be storing the total in your table. The totals should only
appear on forms or reports. Otherwise, you would have to have the total
reclac anytime data is entered.
 
Thank you. This information is helpful. I will need to make some changes to
the way the database is set up and this will help.
 
Thank you. I will make the changes.

John W. Vinson said:
I'm not sure how you're getting the total into the table in the first place -
but you *shouldn't be doing so*.

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.


John W. Vinson [MVP]
Click to expand...
 
Back
Top