<div>
Put<br />
&nbsp; &nbsp; DoCmd.Requery<br />
in the OnExit event of each field.<br />
<br />
Paul
</div>


<div>
Instead of Requery, you would want to use Me.ReCalc if anything.<br />
<br />
mx
</div>


<div>
Put <br />
<br />
Me.ReCalc<br />
<br />
in the AfterUpdate event of any control that can affect the results the calculated controls.<br />
<br />
AU is better than On Exit, because if someone is just tabbing through &nbsp;a control ... and no data is changed, then there is no need to do the ReCalc.<br />
<br />
mx
</div>


<div>
I understand why using AfterUpdate is better than using OnExit. &nbsp;Why is Me.ReCalc better than Me.Requery?<br />
<br />
Paul
</div>


<div>
<div class="content wysiwyg-content">
I have a form which contains 5 different calculated fields. &nbsp;If I make a change to a field which effects any of these calculated fields my sum total field doesn't update. &nbsp;I can force the recalculation of all calculated fields and including the sum total field with a command button on the form with an onclick event of Me.recalc.<br />
<br />
How can I make the entire form and all calculated fields update any time a change is made with the data entry?
</div>
</div>


I have a form which contains 5 different calculated fields.  If I make a change to a field which effects any of these calculated fields my sum total field doesn't update.  I can force the recalculation of all calculated fields and including the sum total field with a command button on the form with an onclick event of Me.recalc.

How can I make the entire form and all calculated fields update any time a change is made with the data entry?

Afterupdate event on a form doesn't recalculate fields

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.