|
| |
For Some, BPI Y2K Problems Are Here Now
Older versions of BPI Accounting Show Their Y2K Flaws in 1999
January 4, 1999 -- The Y2K writing is on the wall now, in 1999, for users of BPI
Accounting
3.0, 3.1, and 4.0.
Because fiscal calendars are edging into the year 2000, earlier versions of BPI
Accounting are
starting to feel their age. Consider the following examples of Y2K problems in BPI version
4.0
that users will experience in 1999:
 | Fiscal calendar displays incorrectly for 2000. Even when 1999 is the current fiscal
year,
the Show Financial Calendar command displays the next year column incorrectly.
If you try to Edit Financial Calendar when 2000 is the current or the next year, you get
an error message saying, "Fiscal Year Must Be Greater than 80 and Less than 99" |
| Date range selector screens don't work. Typical of Y2K problems, BPI 4.0 thinks that
01/01/00 means 01/01/1900 instead of 01/01/2000. It treats as invalid a date range that
spans between 1999 and 2000, as seen below. |
| Aging functions don't work. In the example below, the invoice due date beyond 2000
is not accepted as valid. |
| Financial reports stop at December 31, 1999. That date is shown as the Ending Date
for any financial statement printed for a period after 1999. |
Version 5.0 of BPI Accounting solves these and other Y2K related problems in BPI.
We offer same-day shipping of BPI
Accounting II version 5.0
Call (800) 256-1786 for details. |
