>There's a few things at work here:
>
>- clearly SECONDS() and SYS(2) are currently not time-zone sensitive. It might be a wish list item to include another parameter which would be sensitive to time zone changes.

This is another subject - I agree that it might be a wish list item.

My point was about seconds() and sys(2) inconsistent behaviour relative to the system time changing while FoxPro is running. I see this more as a bug than the time zone sensitivity (which looks more like a wish list item, because the two functions are, at least, consistent).

Regardless, I'd like the SECONDS() to sense system time changes. There was a time when SECONDS() didn't note the passing of midnight, but that has been fixed.

>
>- you could write a wrapper to those functions to handle the case when the time changes.
>
>- maybe there is an API call that returns Zulu (GMT) time always, regardless of the current time zone. You could then make use of that for time difference calculations.
>
>- it could be argued that if you've got an app running 24/7 you should set the time to Standard time, and tell the OS to never update it. You would then need to translate in your application.

The problem is that the 24/7 app runs on one WS, but the records and reports are used on any WS on the network, so we would have to set all WS to never update the time - that is out of question because of all other apps running on the network. Using sys(2) was simple and does exactly what we need - I'm tempted to say VFP doesn't actually need SECONDS() at all, but now it is probably too late to get rid of it.