DC>> That makes the Door problem sound as if it was purely a
 DC>> problem with BW itself.

 ml>> both, the door and the reader had a/the problem... each exhibited
 ml>> different symptoms, though... of course, they both had the same
 ml>> problem because they both use the same time library... that is at the
 ml>> root of the problems...

 DC> Based on what i see in my non-standard setup, the time stamp
 DC> was/is the root of the problem.

yes, and the point that i'm trying to make is that the standard time
library code is at least one place that the fault occurs...

generally, what is done is to take today's year and subtract the epoch of
the library from it... since this was done with only the last two digits of
the year, the subtraction resulted in a value greater than 100 which most
programs just take directly... what they should do is to take the last two
digits of the result but since they don't, the timestamp used in programs
like BW comes out like  "08 Jun 107" instead of "08 Jun
07"... it is a combination of two errors...

 1. taking the entire result instead of just a 2 digit value.

 2. using two digit years instead of 3 digit years.

 DC> It's a shame I can't contact the people that created OMX.
 DC> They seemed to have guessed the Y2K deal and handled it
 DC> before it became an issue.

it isn't any majik, really... if one follows decent practises, one won't
fall into traps like this...

why would you want or need to contact the OMX folk?

)\/(ark