Hi, Rich.
This is a common question from new users. The short answer is you probably
don't need or want to.
There's no need to store a calculation in a field because it can be
calculated on-the-fly in a query faster than you can read it from disk.
Moreover, it can only be done by using VBA code, since a form control can
either have its ControlSource property set to the name of a field OR to a
calculation, but not both.
If any of the data used in the calculation is changed outside the context of
your form where the code is run to update the calculated field, either in the
table directly or through another form, the calculated data will no longer be
correct. So the best way to handle this is to recalculate it in a query
every time you need it.
There are very rare exceptions to this. If yours happens to be one of them,
you would assign the value of the calculated control to the field every time
it changes (i.e., in the AfterUpdate event of each control used in the
calculation):
Me![MyField] = Me![MyCalculatedControl]
Hope that helps.
Sprinks