Hi Ron, > Only as an option. Some of us have only dialup and do not have > continuously > access to the internet. For us folks having dialup not engaged would > probably result in a delay in Dxbase opening.
All I know is I spent the afternoon/evening at my computer with DXbase running. Around 8:30 PM I noticed that posts to the cluster window = didn't match DXbase's clock. Here's what I know: 1. This is not a DXbase issue. It's a computer time issue that can = affect log entries. 2. DXbase was running the whole time and I made no changes in the setup. 3. I checked UTC some time in the early afternoon at http://tycho.usno.navy.mil/cgi-bin/d0clock.xbm. It was correct. I don't = do this very often. I think I will now. 4. Around 8:30 PM I noticed that posts to cluster window did not match DXbase's clock. 5. First thing I investigated was computer time and it was no longer on Eastern Daylight Time. "Automatically adjust clock for daylight saving changes" was checked. But the computer was on Eastern Standard Time. "Automatically synchronize with and Internet time server" was also = checked. I also noticed a note that time had automatically updated at 5:00 PM = that day. 6. I re-synced with time.windows.com and no change. I changed to time.nist.gov and that fixed the problem. Hours later I attempted to see what would happen if I re-synced with time.windows.com. I then got an = error message. I just tried this again a few minutes ago and it worked fine. 7. Yesterday afternoon/evening I made no changes to any software. 8. At no time during this problem did local time change on my computer. Conclusion: Yesterday there was a problem with the time.windows.com = server and Windows XP users should be aware of the potential and/or possible problem. BTW Windows XP only updates time once a week so to have this happen to = you your time sync would have to have been yesterday afternoon. 73, Art W2NRA
