Bug in DateTime

  • Thread starter Thread starter Thore Berntsen
  • Start date Start date
T

Thore Berntsen

I have written a inventory application in C# that was used in 21 stores this
newyear. The data from this application is written to XML. On each item that
is scanned (we use Intermec Pocket PC's) we write the datetime when the item
was scanned to the XML (on each record).

I got about 60000 records form these stores to process. That was no problem.
But on a few of these records I got the year 2204 in the scannedtime element
not 2004. These records could come among records that where ok, and they
were few. Is there a known bug in the DateTime class?

Thore Berntsen
VBD
 
There are no known bugs in .NetCF DateTime class that matches your
description. Do you use DateTime.Now() to capture the time of a scan?
Did you use the same device to scan all items? If not, is it possible that
the time settings on a particular device were wrong?

Roman
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| From: "Thore Berntsen" <[email protected]>
| Subject: Bug in DateTime
| Date: Thu, 15 Jan 2004 10:51:32 +0100
| Lines: 14
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <#[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| NNTP-Posting-Host: 195.204.99.34
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.
phx.gbl
| Xref: cpmsftngxa07.phx.gbl
microsoft.public.dotnet.framework.compactframework:43085
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| I have written a inventory application in C# that was used in 21 stores
this
| newyear. The data from this application is written to XML. On each item
that
| is scanned (we use Intermec Pocket PC's) we write the datetime when the
item
| was scanned to the XML (on each record).
|
| I got about 60000 records form these stores to process. That was no
problem.
| But on a few of these records I got the year 2204 in the scannedtime
element
| not 2004. These records could come among records that where ok, and they
| were few. Is there a known bug in the DateTime class?
|
| Thore Berntsen
| VBD
|
|
|

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top