With due respect to namliam, his method flips out if your answer is longer than 24 hours for a net print job, I think. Unless something has changed in the way Access works on time fields.
In English, your problem is:
Date/Time fields are stored as a relative number - the number of days and fractions thereof between the given date and a reference date.
When you try to do something that results in a field that you think OUGHT to be some kind of time-based thing, you find that the standard date/time formatting routines often go nutzo on you because they AREN'T based on the reference date, but Access doesn't have a way for you to tell it that. It gamely tries to convert your number, only to find that whatever it is, it isn't a "real" date/time fields. 'cause the answer gets a bit bizarre, maybe looks like a date in 1900 - or 1970, depends on more factors than I care to contemplate at this time as to which one.
So the right way to do this and forever ignore Access's stultified view of the world is to build a function that takes some number that you provide and treat it as a number of hours - or minutes - or seconds, you have to decide which when you write it. Never mind real or double, just give it a number of some kind. But ALWAYS of the SAME kind and ALWAYS of the SAME meaning. If you give it long-integer seconds, ALWAYS give it that. Then, when the function gets called, it converts the number to the text format you want explicitly.
Suppose your little routine takes seconds and converts it to text. What you do is build a public string function in a general module. One input argument, which is (for this case) estimated seconds.
So it takes the integer and divides it by 3600. That quotient is the number of hours. Also take the remainder using MOD. Now divide the remainder time by 60. The quotient is the number of minutes. The remainder is the leftover seconds.
Convert those three numbers to text formats. Allow the hours to be five or six digits if you want. Make the minutes and seconds have fixed, two-digit formats with leading zeroes. Concatenate the mess, with each digit string separated by colons. Return the concatenated string as hhhhh:mm:ss.
If this is a public function, you can use this routine in queries, forms, and reports as often as you wish as long as you give it what it wants for input.
