As a basic design issue, you should be aware that Access doesn't manipulate time accumulation very well without a little help and a LOT of understanding. Date fields have an "offset" or "bias" amount - the number of days since the reference date. So you can subtract date fields, but the units are DAYS and fractions thereof. When you accumulate times in that format, Access wants the bias to still be there. Its formatting routines assume that. Incorrectly assume it, of course.... If you are up on your math theory, you know that the difference between two biased numbers will eliminate the bias amount, leaving the true difference behind. So that's good. But the Access assumption regarding that bias is bad.
As part of your design, you CAN subtract times to get time differences. You CAN add these differences to accumulate times. But when you try to format things, THAT step is where the **it hits the fan. 'scuse me, I need to put that in GovSpeak to be more polite - where the foetid biological mixed-phase ejecta impacts the blades of the rapidly rotating atmospheric destratifier.
Anyway - the units of the differences (and therefore of the accumulation) will be days and fractions thereof. To convert this to hours, convert the date to DOUBLE format (see function CDbl). Multiply it by 24 to get hours and fractions, in which case you can just format the output to a convenient number of decimal places past the hour. One or two should be plenty. But don't assume that you can quite so easily convert that number to HH:MM format without some specialized code.