Year 2000
Compliance Assessment
Product:
Find and Replace for Microsoft Access
Version:
2.0: 2.07h and later. 7.0: 7.00e and later. 8.0: 8.01c
and later, 9.0: 9.00 and later.
Year 2000 Compliance means
that neither performance nor functionality of this
product is affected by dates prior to, during and after
the Year 2000. The following assessment identifies date
functionality by categories using statements describing
Year 2000 Compliant date capabilities within each
category.
The following dates are
significant to Year 2000 Compliance. In the assessment,
these are referred to as Y2K or high risk
dates:
| Single Dates |
Rollover
Dates |
Significance |
|
| 1999-01-01 1999-09-09
|
1998-12-31 to 1999-01-01 |
Potential
extended semantic value, e.g., year 99 means
"no expiration date" |
| 1999-12-31 |
|
Last
day before century |
| 2000-01-01 |
1999-12-31 to 2000-01-01 |
First
day of century |
| 2000-02-28 |
|
Day
before Leap Day |
| 2000-02-29 |
2000-02-28 to 2000-02-29 |
Leap
Day |
| 2000-03-01 |
2000-02-29 to 2000-03-01 |
Day
after Leap Day |
| 2000-12-31 |
|
Last
day of Leap Year |
| 2001-01-01 |
|
First
day of year after Leap Year |
| 2027-12-31 |
|
Upper
limit day for some systems |
| 2038-01-19 |
|
Upper
limit day for some systems |
| |
Compliant? |
| 1.
Calculations for Y2K Dates |
Yes |
Some |
No |
N/A |
|
| 1.1
Calculates the duration between two dates |
[
] |
[
] |
[
] |
[x] |
| 1.2
Calculates date based on starting date and
duration |
[
] |
[
] |
[
] |
[x] |
| 1.3
Calculates day of week, day within year, week
within year |
[
] |
[
] |
[
] |
[x] |
| 1.4
Compares two dates for sequencing or equality |
[x] |
[
] |
[
] |
[
] |
| 1.5
Other |
[
] |
[
] |
[
] |
[x] |
| |
Compliant? |
| 2.
Data Storage for Y2K Dates |
Yes |
Some |
No |
N/A |
|
| 2.1
Stores and retrieves dates |
[x] |
[
] |
[
] |
[
] |
| 2.2
Moves date data within RAM |
[x] |
[
] |
[
] |
[
] |
| 2.3
Sorts and merges dates |
[
] |
[
] |
[
] |
[x] |
| 2.4
Searches dates |
[
] |
[
] |
[
] |
[x] |
| 2.5
Indexes dates on disk file or database table |
[
] |
[
] |
[
] |
[x] |
| 2.6 Other |
[
] |
[
] |
[
] |
[x] |
| |
Compliant? |
| 3.
Date Values |
Yes |
Some |
No |
N/A |
|
| 3.1
Does not use date variables for any purpose other
than storing date information |
[x] |
[
] |
[
] |
[
] |
| 3.2
Does not use "99" as special value for
year |
[x] |
[
] |
[
] |
[
] |
| 3.3
Does not use "99.365" as special value
for Julian date |
[x] |
[
] |
[
] |
[
] |
| 3.4
Does not use "00" as special value for
year |
[x] |
[
] |
[
] |
[
] |
| 3.5
Initializes all date elements with all zeros or
as null (preferred) |
[x] |
[
] |
[
] |
[
] |
| 3.6 Handles Leap
Years (Leap year is either evenly divisible by
400 or evenly divisible by 4 and not evenly
divisible by 100 (e.g. not 1800, not 1900, yes
2000) |
[
] |
[
] |
[
] |
[x] |
| 3.7 Specify the
minimum acceptable date value: |
January 1, 1900 |
| 3.8 Specify the
maximum acceptable date value: |
December 31, 2099 |
| 3.9 Other |
[
] |
[
] |
[
] |
[x] |
| |
Compliant? |
| 4.
Date Representation for Y2K Dates |
Yes |
Some |
No |
N/A |
|
| 4.1
Handles conversion between date representation
(YMD, Julian, etc.) |
[x] |
[
] |
[
] |
[
] |
| 4.2
Explicitly represents the century of a date, e.g.
uses a 4-digit year or includes a century
indicator (i.e. explicit century) |
[x] |
[
] |
[
] |
[
] |
| 4.3
Infers the century of a date is by a specified
rule, e.g. defines two-digit years with a value
greater than 50 imply 19xx, whereas those with a
value less than or equal to 50 imply 20xx.
Applies the rule to all contexts in which the
date is used (different rules may apply to
different date sets). Documents the rule for
users (i.e. implicit century) |
[
] |
[
] |
[
] |
[x] |
| 4.4
Handles user interface functionality (e.g.
formatting display of date on screen, in reports) |
[x] |
[
] |
[
] |
[
] |
| 4.5
Other |
[
] |
[
] |
[
] |
[x] |
| |
Compliant? |
| 5.
General Product Integrity for Y2K Dates |
Yes |
Some |
No |
N/A |
|
| 5.1
Handles all values for system date between
1985-01-01 and 2035-12-31 |
[x] |
[
] |
[
] |
[
] |
| 5.2
Roll-over between all significant time
demarcations (days, months, years, centuries)
performs correctly |
[
] |
[
] |
[
] |
[x] |
| 5.3
Handles evaluation copy "expiration
date" |
[x] |
[
] |
[
] |
[
] |
| 5.4
Other |
[
] |
[
] |
[
] |
[x] |
| |
Compliant? |
| 6.
General Data Interfaces for Y2K Dates |
Yes |
Some |
No |
N/A |
|
| 6.1
Handles transfer of dates from/to the operating
system |
[
] |
[
] |
[
] |
[x] |
| 6.2
Handles transfer of dates from/to other
applications |
[
] |
[
] |
[
] |
[x] |
| 6.3
Provides "bridge" functionality to
translate or converts dates from/to other
applications if necessary |
[
] |
[
] |
[
] |
[x] |
| 6.4
Other |
[
] |
[
] |
[
] |
[x] |
| 7. Comments |
|
| Assessment Date: 11/98 |
|