Don’t know if I should post this as a solution.
disask119426DateTimeIntervals.ods (33.9 KB)
The most important additional hint: Never use a TOD format like HH:MM:SS what unfortunately is a kind of standard though it hides a possibly existing integer part which may go back to a slightly trembling finger during input.
Since we have lots of related questions over the years (here and also in the AOO forum), and contributors have already wasted thousands of hours with inventig (re-inventing) little wheels just modified to support any very special need, I feel tempted to teach about the reasons for such a mess.
Surely it is not the lack of support for a “[DD]” format code. Dates are dates after all, and everybody should know the clever way to write them (ISO 8601), but few do…
Well, decide yourself if the suggestions, formulas, and explanations contained in the attached document are of some use, or just another example for wasted time.
Oh my! Even the British managed to get rid of their outdated currency system with funny subdivisions of 20, 12, and … more (coins). But:
Part of the mess with TOD (TimeOfDay) and durations goes back about 4000 years when a then progressive civilisation preferred subdivisions by 60 (“sexagesimal”). This was rather clever then because the divisor contained all the factors 1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30 what helped to avoid calculations with additional fractions in many cases. Later Leibniz considered a base of 12 better than the 10 we are using for the same reason.
Now computers do the calculations for us without complaining about a base o 10 or one of 2 (though there are disadvantages of the dyadic system, too).
A centiday (1cd = 1d/100 = 14.4 min = 14 min 26 s) would be a handy unit, wouldn’t it? Just wait another 1000 years.