Hi Bernard,

We have one customer with a similar problem.

FPW 2.6 legacy stuff with a an "end of day" maintenance routine that runs normally from any other machine on the network (WIN2k,XP machines), but will not even 'kick off' at the designated time if run directly on the WIN2k SP3 server.

It looses time at about the same rate as you are seeing and never reachs the designated 11:30 PM start time before the early workers arrive the next morning.

We have never figured out why this happens and fortunately the customer hasn't forced the issue on running the routine directly on the server.

Wish I could supply a solution, but maybe someone else has a clue.

Regards,

Tom

>Hi Guys
>
>We are running a legacy FPW2.6 application on WIN2K servers using RDP. The EXE and DATA is all stored on servers and users on the WAN log in to a "FARM" of servers (5)to access the app.
>
>The problem we have is that on one of the servers only, the TIME as displayed and stored in FPW is slowly losing time as compared to the server. This does not happen to VFP7 applications and does not happen when users are logged in to other servers in the farm running the same app and using the same data.
>
>The slowdown is easily visible and FPW loses a second approx. every 2 seconds so that in an hour of running it behind the server time by 1/2 hours.
>This strange phenomen is NOT occuring on any of the other 4 servers.
>
>Does anyone have an idea why/how this is happening and where I might look for some info about this?
>
>Thanks Bernard