Quote:
> I have a problem I cannot pin down yet. I know nnetsdate() failed the y2k
> rollover. When I disabled this function in an employee time clock program
> and let the time come from the pc system date, with two days
> inactivity(the weekend) the computer lost two days. Meaning at the dos
> prompt, date showed the incorrect date. When I immediately reboot and go
> to the bios setup it shows the correct date. My dos computers are all ver
> 6.22. Is this a problem I have had all along and when Jan 1 rolled over
> and nnetsdate() failed I finally found it? This program monitors a com
> port and reads a barcode scan. Is it causing dos to not roll the days. The
> time is staying right.
This is a pretty commonly seen and known problem (a search of the archives
over at DejaNews <URL:http://www.deja.com/> will probably lead you to past
discussions the subject).
What you need to do (and it isn't just a problem with your Clipper app, it
is a general problem) is in the polling loop (I assume you're referring to
some form of polling loop in the above) make sure you make a call to date()
every so often. Doing so ensures that DOS's view of the current date is
correct.
PS: When doing that DejaNews search look for "midnight rollover".
--
Take a look in Hagbard's World: | w3ng - The WWW Norton Guide reader.
http://www.acemake.com/hagbard/ | eg - Norton Guide reader for Linux.
http://www.hagbard.demon.co.uk/ | weg - Norton Guide reader for Windows.
Free software, including........| dgscan - DGROUP scanner for Clipper.
Date does not rollover