>Cetin,
>
>>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.
>
>You are right about SECONDS() not changing when system time is changed. However, if the app is closed and run again, SECONDS() then follows the system time at the instance.
>
>
>>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).
>
>Am very curious on what you said about being easy to change system time even under XP/NT, if I restrict Change System Time policy and put a password on the CMOS bootup, how else can one change time?
>
>Thanks
>Dennis

Considering you left your box for a few minutes for my physical reach :
-Would open the cover and clear CMOS with the help of a jumper or screwdriver
-Go to setup and set the clock

Well you'd understand something has happened as it wouldn't ask for password on power up but might also set a password when I went to setup and you'd go nuts seeing it doesn't accept your pw and probably would go to clearing CMOS yurself too :)
PS: There are BIOSes that doesn't even need such a clearing of CMOS. They accept a special sequence of chars as pw whatever the actual pw is.
And really how many setup a CMOS pw especially if the box is NT/XP:) I don't for example.
Cetin