Storing a calculated field in a table

[Dorothy]

Is there a way to store a calculated field in a table? I
have a form with a field of "Date rec'd" and another field
of "Date Due to Mgr." The Date Due has a calculation in
the properties where it adds 3 days to the Date Rec'd. I
would like the result of this to be stored in the table.
Currently, it is not being stored. The Date Due appears on
the form correct, but when I open the table it appears
blank.
Please help. Thanks

 

[Graham Mandeno]

Hi Dorothy

You should do nothing. The design is currently correct.

Create a query with a calculated field:
[DateDueToMgr]: [DateRecd] + 3
....along with all the other relevant fields from your table.

Then create a form based on your query and don't ever let your users
anywhere near your tables and queries.

 

[Dorothy]

-----Original Message-----
Hi Dorothy

You should do nothing. The design is currently correct.

Create a query with a calculated field:
[DateDueToMgr]: [DateRecd] + 3
....along with all the other relevant fields from your table.

Then create a form based on your query and don't ever let your users
anywhere near your tables and queries.

--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

Is there a way to store a calculated field in a table? I
have a form with a field of "Date rec'd" and another field
of "Date Due to Mgr." The Date Due has a calculation in
the properties where it adds 3 days to the Date Rec'd. I
would like the result of this to be stored in the table.
Currently, it is not being stored. The Date Due appears on
the form correct, but when I open the table it appears
blank.
Please help. Thanks

.
Thanks Graham. I actually did just what you said earlier

today, but I thought there would have been a way to store
the info in the original table, but I guess not. Thanks
for your response.

 

[Graham Mandeno]

Hi Dorothy

Thanks Graham. I actually did just what you said earlier
today, but I thought there would have been a way to store
the info in the original table, but I guess not. Thanks
for your response.

Sorry - I think you missed my point. It is certainly *possible* to store a
calculated field in a table, but it is something you *should not do*.
Firstly, it wastes space (not really a problem these days , but more
importantly, it provides a window for loss of data integrity. If someone
updates the DateRecd field, but the code to calculate and store the DateDue
field fails to run for some reason, then the data in your record is WRONG.