Skip to Content
Former Member
Aug 13, 2007 at 04:36 PM

A glitch(?) or "feature"(?) in SD_CALC_DURATION_FROM_DATETIME


SD_CALC_DURATION_FROM_DATETIME works fine except for customers who want to be able to enter 24:00:00 as a valid time on a screen field defined with a custom data element that has a "TIMS" type underneath it. (I need the custom data element to get custom F1 documentation help.)

In this case, SD_CALC_DURATION_FROM_DATETIME adds 24 hrs to the calculated duration.

There are, of course, any number of obvious work-arounds but am curious as to why this functions seems to behave this way and if anyone else has noted this glitch(?)/feature(?).

Also, whether there is another function without this feature(?)/glitch(?) that calculates duration to the second ... ????

Thanks in advance for whatever anyone knows about this matter ...