We have several (not all) XP computers starting to return wrong time (fast/slow by several hours)while using TCL TIME or TIME() function call within the programs. Once the user exits and re-launches AREV the clock time returns the real time.

All our XPs are same versions and computers are all DELL with almost identical configs. I have come across a discussion thread here, but apparently without a clear solution.

We do run Mcaffe Virus scanner for updates and thats the only piece of software upgrade we have had prior to surfacing of this "TIME()" problem.

We have checked our three domain controllers and they are reporting the correct time. As our Order Entry system is dependent on real time, the matter is of utmost important to us.

Any inputs would be greatly appreciated.

Raju T.

We had a similar problem with an application based on Arev 3.12 running on a Dell Win2k SP3 server. A system update program would run on the server every night, creating a small log file. The first entry in the log file is the starting time of the program (always correct). The last entry in the log file is the duration in hours and minutes of the program. Suddenly this value was short by 1-2 hours. As soon as we applied Win2k Service Pack 4 to the server, the problem resolved itself.

You can re-sync the time in other ways. I recall other threads here in this forum about how to do this for Windows and Novell networks - by using your server clock as the primary source, or even an external naval clock across the internet as the primary source.

I have an application that gets the time from the OS.

In Win98 the time is correct.

In XP the time is incorrect.

The clients are waiting for a fix. Not a major problem but it is annoying.

A service pack 4 fix for W2K has been mentioned in a prior post.

Is there a service pack fix for XP.

View this thread on the forum...