>>>>>I ask, because 4.x has a utility called systime which we run at login and causes the client system to set it's time to the server's time.....
>>>>
>>>>What's to stop the user from changing the time after they log in? We had this happen. The boss said "We have to fix this immediately" So, we bought GPLib and we now pull the time from the server. We'll need a different methodology when we go to an NT server, but it shouldn't be difficult to use an automation server.
>>>
>>>I thought the question was: 'How do I reliably ensure all my workstations' clocks are set to the same time?'. You'll *never* get around an obnoxious user....
>>>
>>That's my point...you can't reliably ensure they are the same. The way to have a reliable time is to replace all the DATE(), TIME() and DATETIME() calls with something that gets the date and time from the server.
>
>I suppose...
>Personnally I'd rather threaten a user than have to worry about rewriting a bunch of code whenever I change server software...
>
>MHO,
>Paul M.

People don't always have the luxury of threatening the user. And this doesn't stop anyone from doing this on purpose. In my case, there could be serious legal problems if the date and time are wrong.

And there really isn't a rewrite. Create one function, that checks what network you're on. If on Netware, run NetLib or GPLib and get the result...if on NT, call the function on an Automation server running on the NT server.