Ok...I have two different AL's performing the same function, with slightly different input. The first is using information in a column representation of a Date/Time field as the start time, then takes that output and /3600 to give you the business hours elapsed. <ACTL> Process: Application-Bus-Time-Diff "1/2/2007 8:20:52 AM" "9/26/2008 2:14:00 PM" "Holiday Schedule" " Weekday Schedule " <ACTL> Duration (900109526) = 12952388 <ACTL> 1: Set Fields <ACTL> Duration (900109526) = 3597 The second action is actually on the form that contains the Date/Time field...same scenario...but this time I notice it uses the epoch value instead of the 'local timezone converted value' like the column display of the information is. If I do a conversion of 1167751252 I'm told it equals "1/2/2007 8:20:52 AM" (in my time zone) <ACTL> Process: Application-Bus-Time-Diff "1167751252" "9/26/2008 2:14:29 PM" "Holiday Schedule" " Weekday Schedule " <ACTL> Duration (Business Hours) (900601624) = 12945217 <ACTL> 1: Set Fields <ACTL> Duration (Business Hours) (900601624) = 3595 The difference between these two calculated values is 7171, which is not quite what I would call a 'round' number as far as time is concerned. Both values are calculated using the 7.1 Patch 3 user tool against a 7.1 Patch 3 server. I'm in Mountain Time Zone....has anyone experienced anything similar and know what's going on?
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
