>But... THIS DOESN'T WORK! A :PAUSE of 65 seconds apparently does not
>guarantee that we have gotten to at least 23:01. At least on this
>customer's system it frequently fails to do so.
Is your customer's system, by any chance, a multi-cpu system?
We've run into a problem where the clocks on the two systems don't
entirely agree, resulting in a program's calling the CLOCK intrinsic
and getting out-of-order return values on consecutive calls, looking
just like time moved backwards a bit.
As I recall, there's a patch (sorry, no ID recollection) that
solves/lessens the problem.
If nobody can find the patch ID, I can contact our customer next
week and find out what he installed.
--
------------
Randy Medd
Telamon, Inc.