hmmmmmmmmmm ... it does "work" if applied properly. On the other hand, I didn't notice any 'helpful hints' toward that "popper' application, and think the user who needs to post the question MAY not instantly recognize the subtle necessities of that application.
To wit, the question shows the calculation in the standard "short time" format, whilst the procedure requires a long data type. The short time format is in fact the 'decimal' portion of a double, so sending the 'results' of the original (or correctd) post will simply result in 0 Hr and 0 Min.
for example:
? RoundTime(#15:52:50#)
0 hrs 0 min
So, some adjustment appears to be necessary to actually have the procedure utilize the 'value' from the original post and return the desired value. A number of different ways to do so, one (rather shakey approach) might be:
? RoundTime(dateDiff("n", StartTime, EndTime))
16 hrs 0 min
However this will (for those not familiar with the generic behaviour of Ms. Date/Time calculations may give an occassional incorrect answer, as the return value counts the number of
transitions of the time unit, and does not 'round' the answer, so a slight difference in expected and actual returns MAY occur:
MyStrtTm = #6:14:33#
MyEndTm = #22:06:31#
? Format((DateDiff("s", MyStrtTm, MyEndTm)/86400), "hh:mm:ss"

15:51:58
? RoundTime(dateDiff("n", MyStrtTm, MyEndTm))
15 hrs 45 min
MichaelRed
m.red@att.net
Searching for employment in all the wrong places