In my database, I enter demographic information on individual customers based on data they supply. The database contains the fields "age" and "birthdate." I am aware that "age" can be set up as a calculation field based on "birthdate." However, I do not have the date of birth data on all the customers but I do have each person's age. I therefore set up the field "age" as a number field with auto-enter calculation (using "birthdate" to calculate the age of the person). In this way, the field can still be entered and the age entered directly if the date of birth is unknown. (obviously, can't do this if the field "age" is a calculation field.)

My problem is that the field "age" does not update (as the database ages) even with the box unchecked for "do not replace existing value of field." It will only update if I go to the record and enter the field "birthdate" and force an update. I would like the field "age" to update automatically without having to enter each record. Is there any way to do this without making the field "age" a pure calculation field?

I believe you should have three fields, the third one being an unstored calculation, along the lines of:

Case (

birthdate ; < calculate the age from birthday > ;

age*

)

---

(*) If you also have a field for 'age as of when', you can use it in the second part of the calculation - so that individuals without a birthdate keep aging, too.

Thanks for the response. I haven't created a third field, as you suggested, to avoid having two "age" fields on the layout. I was hoping to have a single field (auto-enter calculation) that would update. I have a feeling, this is not possible.

No, a stored field will not update as the result of mere passage of time. That is a good thing, when you think about it. Also, it is convenient to keep record of the original input, just in case.