Actually, the answer is much simpler than this DAYS, HOURS, MINUTES, SECONDS silliness.
You already have the Opened and Resolved date/time, except some jerk added SPACE "at" SPACE between the date and time, probably someone's boss who wanted it to be "readable" rather than "usable"
So I replaced the SPACE "at" SPACE with a delimiter, added a column and parsed the Opened and Resolved each into date and time, like this...
[pre]
Incident Incident Type Opened oTIM Closed cTIM delta Seconds
rby-rw-rtr-2 Rural Wireless 7/1/2016 20:15 7/1/2016 20:17 0.001388889 120
sva-rw-msc-1 Rural Wireless 7/5/2016 17:26 7/5/2016 22:04 0.193055556 16680
sva-rw-img-1 Rural Wireless 7/5/2016 17:27 7/5/2016 20:58 0.146527778 12660
sva-rw-rtr-2 Rural Wireless 7/5/2016 17:28 7/5/2016 20:58 0.145833333 12600
sva-rw-rtr-1 Rural Wireless 7/5/2016 17:28 7/5/2016 20:58 0.145833333 12600
pho-rw-msc-1 Rural Wireless 7/6/2016 9:18 7/6/2016 15:50 0.272222222 23520
pho-rw-img-1 Rural Wireless 7/6/2016 9:27 7/6/2016 13:15 0.158333333 13680
enm-rw-rtr-1 Rural Wireless 7/6/2016 12:36 7/6/2016 13:28 0.036111111 3120
pho-rw-img-1 Rural Wireless 7/6/2016 13:31 7/6/2016 13:51 0.013888889 1200
[/pre]
Then I just convert days to seconds (days * 24*60*60)
It rub is that I disagree with every one of your hours, minutes, seconds be a few seconds, ALL a different number of seconds as you can see.
Skip,
Just traded in my OLD subtlety...
for a NUance!![[tongue] [tongue] [tongue]](/data/assets/smilies/tongue.gif)