Yes,
Once VFP launched any changes in time are not reflected in seconds(). sys(2) reflects them. So comparing the 2 you could say that time was set back (or forth) and act accordingly. You could silently set the system time with winAPI.
However if time was gotten back before VFP's launch there is nothing you can do about it. On a standalone PC (really standalone) with an OS like win9x there is no bulletproof prevention of playing with the clock. You might enforce the policies but a clever user knows he doesn't need the windows to change the time (actually in NT,XP too it's easy to change the time no matter how much strict policies exist).
Cetin

>Cetin,
>
>I didnt know that SECONDS() functions works independently and entirely oblivious to the System Time of a PC!
>
>Will check this out and get back to you. Thanks
>
>Dennis
>
>>As per reply to Hilmar I read it was standalone. Then you might utilize seconds() function. It doesn't get updated by setting time in control panel. As you detect a warp in time you could set it back to correct time using winAPI.
>>PS: Use sys(2) for updated value.
>>Cetin