The clock in Windows
-
How can I do an app or just something that makes it impossible for the user to change the time?? Is that possible?
In windows you can trap time changes, but it isn't cut and dried, you have to know what time it was previous to the user changing it if you want to turn the clock back. This is of cause a rediculous way to treat time with obvious risks involved. In Win2000 (and family) the standard user by default does not have access to change the time. This can be important, since time is important to networks and very much so to databases. Rather than trap-then-reset the clock, what you need is a time source. If you have a network then you make one of the servers a time server. Did you know that Windows only looks at your clock once? One of the first stages of Windows startup is to look for the network, this is when it would pickup from a timeserver, if no timeserver then it looks at your realtime clock. That is the last time it looks. If you don't have a server. There is a time source on the internet, I can't seem to recal where it is off the top of my head but Grenich would be the place to start looking (or your local counties equivelent time station). Question for NT client guru's? Can the client be setup to timeserve? I remember seeing a white paper where it was mentioned many moons ago, but I don't know if its been implemented. I suspect it has, because of database sharing in PC-PC networks. We do it for the joy of seeing the users struggle.