Rather than grabbing the century from the system clock, it looks like the
program uses a "pivot date" of 90 - that is, anything from 90 - 99 is 20th
century and anything 00 - 89 is 21st century. The program wasn't
originally written / released in 1990 by any chance, was it?
I think that the OP is running ACCPAC version 6. Version 5 and below
assumed that all dates were 19xx; version 6 splits the centuries at 1989/90.
Presumably the intent was to preserve the batch input format between
versions; it uses a 2-digit date. It's not particularly well documented (a
characterization that covers much of the ACCPAC product...) but in version 6
the date is windowed to support dates from 1990 through 2089. You can see
this by attempting to print batch reports between dates of 12/31/89 through
12/31/99 (fails; "start date not prior to end date") and 01/01/90 through
12/31/99 (works). V6 carries a 1993 copyright date.
The places where "today's date" is used it acts on 2-digit years. As far as
I can tell it doesn't make any use of the century from the hardware clock
except for the date display in the page and screen headers.
If the OP really does need to work with the 1989 data and can't find a copy
of ACCPAC version 5 (IIRC version 5 introduced several features missing in
earlier versions, and uses a different input and report format compared to
v4) then it might be possible to bludgeon it into working by re-editing the
fiscal calendar (HOUSEKEEPING -> EDIT COMPANY PROFILE) on he off chance that
it would make "89" valid.
On the other hand, it may be that year "89" has a boundary case problem and
can't be made to work. If the 1989 transactions are available as batch
input files, you could manually edit each line to window them to another
year (say, "39" for 2039, a 50-year bias), process them, then interpret the
reports by subtracting 50 years from any date. Kludgy, but if this is a
one-time (or at least very infrequent) process it might be easier than some
other options.
Then there's the obvious suggestion that the OP (or his employer, or
customer) just bite the bullet and scrap ACCPAC in favor of a more recent
product. Maybe even ACCPAC for Windows (which I've never used).
BTW: my experience is exclusively with the GL component, but presumably the
others (AR, AP, etc.) share the same date behavior.
Joe Morris