I wonder if the fact that changing the system time while FoxPro is running is not reflected in the SECONDS() is considered a bug or a wish list item.
I know that, in general, it is not a good idea to change the system time while FoxPro is running , but for here is one instance when this is legitimate:
We have an unattended app running 24x7, and two days ago, the OS on the WS changed the time to the daylight saving time. The app, using SECONDS(), recorded the seconds as if nothing changed, one hour behind. Fortunately nothing critical happened, but it could have been the case.
I replaced SECONDS() with SYS(2), but I think SECONDS() should work the same too.