| The Year 2000 problem refers to the inability of many legacy systems
to handle the date change from December 31, 1999 to January 1, 2000. The problem arises
from the fact that legacy code commonly uses only two digits to represent the year of any
given date. Year 2000 compliance means that date information is accurately processed from,
into, and between the twentieth and twenty-first centuries.
All Objectmatter products are year 2000 compliant as long as they are used in
conjunction with hardware, operating systems, databases, and database drivers that are
themselves year 2000 compliant.
VBSF and BSF store dates internally using the java.util.Date date type, which
maintains the number of milliseconds since midnight, January 1, 1970 to represent the date
and time. This method does not suffer from any year 2000 problems. Both products have been
successfully tested to store and retrieve dates before and after December 31, 2000. The
only problem found has been with Microsoft Access 97 under the JDBC/ODBC bridge and ODBC
driver v3.51.102900, in with case dates after the year 2000 are not properly stored. |
