Re: .. Y2K and databases

Chris Young <c.young@virgin.com> wrote in article <01bc73d6$0ef89920$803ca8c2@default>... > Everyone seems to be concentrating on source code but ignoring the other > major problem - dates in the database. You must be joking! Have you been following the Y2K debate? > In light of this I developed a tool to scan most of the major databases > (mainframe, AS/400, Access, etc.) which I am now making available as an > inexpensive utility. Good for you. > "Datefind" uses ODBC to connect to the database (so works on any database > that has an ODBC driver available) and scans ALL files finding dates which > are NOT Year 2000 compliant. Really? How does your program recognise an 8-bit integer field that contains a two-digit year? Or a character field in which some idiot decided to store a years-since-1900 value in base-36 arithmetic? > I hope this tool saves you as much time as it has saved me. How lucky you are... -- Gregory D. Hawkes <rivergum@geocities.com.despam> (Remove ".despam" when replying, please)