I don't believe that is what Paul suggested. He was saying put the SYSTIME command in the container login script so the workstation gets synchronized when the user logs in. Do not place SYSTIME in your VFP app.

>I could do that, but the form that is running has a button to allow the user to logout for lunch and on to log in from lunch. So I waould have to synch. the times multiple times during the execution of the program, not just at login.
>
>>>Hi all,
>>>
>>>I need to pull the date and time off of a Novell 4.11 server. I don't want to purchase any 3rd party libs. (If you know of a freeware, I'm interested.) Anyway, (with some help on the idea) I put together a routine that would create a file on the server, get the date and time from it, then delete it. This works great until I realized that I was going to use up all of the deleted space on the server. Then I looked at running purge at the end of the routine, but I couldn't get rid of the finished box. Even if I use WinExec with the 0 parameter, after I run it, I had to Ctrl+Alt+Delete and End Task on Winoldap. (or something like that) Then I tried running SysTime and piping it into a file on the local drive. It works with the run command if I don't use the /N or /N7 (or any variation). I also tried it with the WinExec. If I WinExec SysTime, it works fine. But when I WinExec SysTime>FileName, WinExec returns 0. Any ideas on where to go next?
>>>
>>>TIA
>>
>>Why not run SYSTIME when the user logs in (using net$log.dat)? That way, the local machine will be set to the same time as the server and you can get reliable time from the local machine...
>>
>>HTH,
>>Paul M.