In a query you just do
Field: Master.FieldName + Transaction.FieldName
In an update query you update the field to the calculation.
A problem here is that you cannot use aggregate functions in an update query
in Access, so if you are trying to sum the information in the transaction
field before you add it to the master field you will have a problem.
As John Vinson was trying to point out, you will have to be careful that you
keep the calculated data up to date. I understand your point about
accessing multiple records, but you might try the suggested solution and see
what kind of performance you are getting - you might be pleasantly
surprised.

Signature
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
.
> John,
>
[quoted text clipped - 42 lines]
>>
>> John W. Vinson [MVP]
Pat Backowski - 26 Nov 2007 17:26 GMT
Thank you, John. I was trying to add and update in one query, hence my
frustration.
I will keep in mind what you and John mentioned regarding not storing
derived data. I'm not sure how it would save disk spins and cpu cycles to
have to re-add balances, constantly, but I'm not too old to learn new tricks.
Many Thanks,
Pat.
> In a query you just do
> Field: Master.FieldName + Transaction.FieldName
[quoted text clipped - 57 lines]
> >>
> >> John W. Vinson [MVP]
John Spencer - 26 Nov 2007 18:31 GMT
It doesn't save disk spins and cpu cycles.
It does help to ensure your data remains correct (in sync with the data that
the sum is derived from)

Signature
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
.
> Thank you, John. I was trying to add and update in one query, hence my
> frustration.
[quoted text clipped - 75 lines]
>> >>
>> >> John W. Vinson [MVP]