You could put it in as a calculated field, in the query or on the form. Wherever makes sense, is simple and has the right level of re-usability. If the calculation is specific a form or view of the data, do it there or in the query.
In this case, you can foresee that the total will be an oft used value and logically applied to the row, so making it a calculated field is appropriate. Calculated fields have the advantage that (in most systems, not sure about MSAccess) they can be set to only re-calculate when the data changes.
If you were working out say the ratio of the quantity vs delivery lead time, that would be more something I would put in the query for the specific form/report as it's never going to be re-used and may be a more hefty calculation.
I would usually choose to do a calculation in the query, unless it relies on the result of another calculation, then doing it in the query could get kinda messy, so do it in the form/code.
So in summary, wherever appropriate for that calc.