HELP! YEAR 2000 BUG: How will it affect you?

Hi, [Note: I am trying to insure that my question reaches a wide database audience, and so am using two different subject contents. This message is identical to the previous one sent by me; if you've read that one already, my apologies - you can skip this one] I am currently preparing a graduate paper on the impact of the Year 2000 (Y2K) bug on databases, database applications, and database management. Specific areas of interest to me and the group to whom it will be presented are: Active Databases, Knowledge Discovery and Data Mining, Data Warehouses, Deductive Databases, Fuzzy Databases/Logic/Queries, GIS, Image Databases, Knowledge-bases, Online Databases, OO Databases, and Text & Document Databases. If you work with one or more of the above, and have specific examples of how the Y2K bug is going to affect you, the database(s), or the way you do work, and how you (or others) are specifically addressing the problem, would you please respond either on the NG or via e-mail (address below, too)? If you don't know about Y2K, but can at least give me an idea of how data with date fields or date information is used in any of the particular specialties above, whether your particular area of databasing uses primarily two-digit date fields, and the potential impact of having the year field "roll-over" to "00", that would be just as good. Any and all assistance will be most helpful. Thanks, Matt Bovee University of Kansas Lawrence, KS mbovee@ukanvm.cc.ukans.edu (or if the first address fails, try mbovee@ukans.edu or mbovee@eagle.cc.ukans.edu)