Join us now to get access to all our awesome features. Once registered and logged in, you will be able to create topics, post replies, give reputation to your fellow members, get your own private messenger, and so, so much more.
Already a registered member but you forgot your password? Click Here!

I din’t know if to hijack this thread or start my own, but this is what I use to try and keep track of the lenght each program runs. It is in Hrs, Mins, Secs. Although I don’t think hrs has ever been anything above zero.
This goes in the beginning of the program.
ASSIGN/STARTTIME=INT(SYSTEMTIME("HH") * 3600) + INT(SYSTEMTIME("mm") * 60) + INT(SYSTEMTIME("ss"))
This goes in the end of the program.
This little code will place the actual run time in the report. If it means anything to anyone, If not I’ll just crawl back to my corner lol.Code:ASSIGN/TOTALTIME=(INT(SYSTEMTIME("HH") * 3600) + INT(SYSTEMTIME("mm") * 60) + INT(SYSTEMTIME("ss")) - STARTTIME) / 60 COMMENT/REPT,"RUN TIME = "+TOTALTIME+" MINUTES"
Ok, some more testing, and some more errors. Using Integer gives me an overflow error when it goes to grab the TIMER number from the computer. This does not happen in excel. I have yet to try to shorten the Timer number using Clng first, then assign it to an integer.
I put parentheses all around my functions, just in case. I had a part run through midnight on Friday and guess what? It's a negative number now! Ex. The start of the program was 86000 seconds from midnight. The end of the program was 1000 seconds from midnight on the next day. The correct calculation would be a runtime of 1400 seconds.
Previously this would have given me the result of 87000 seconds. Now it gives -85000 as the result.
So, continuing forward, I will try to get this working with integers, and test it then. Thanks for the help guys.
Bookmarks