>>Let's take a step back here and see if I understand what you're doing. Do I understand that the user is entering the result of a calculation? And that all the data to calculate the result is available to the program? If that's the case, why is the user entering the result? Just have the program calculate the total. You can have the program store the result in the table, then just add or subtract each time and keep the total update.
>>
>>Craig
>
>Actually Craig, and Sam can correct me if I've got it wrong, I believe that he performs a colculation based on a user's input and then shows the result of the calculation to the user prior to saving. I would imagine that he wants to give the user the ability to change the input again if the output was not what was expected, kind of a reverse engineering.
>
>I think George had it right if all of the inputs come from the table, then the result should not be stored at all. It should be calculated with a function that gets called in SELECTs, forms and reports.


There are times when calculations should be stored. I think this is one of them. If he is having problems calcualting the results each time...ie: it is time consuming...then he has a need to store the calculation. He should also have an option to recalcuate on the fly...just in case something goes wrong and the total get corrupted....or an option to recalculate all of the totals. Each time a new number is entered, it should be added or subtracted from the total.

Craig