A client has recently noticed that the report date in the top right corner of their Adagio Payables reports is not displaying properly and is displaying a bogus December date. The transaction details appear to be fine, just the report date seems to be the problem.

The date format was changed to see if that was the problem but the results are similar.

The display and printing showed the following:

Dec 31-4714 or -14/12/31

This appears to have started sometime during the month of April. The version is 6.8A (011206)

No other module is affected and the program seems to be running fine otherwise.

Dear MLS

If the other Adagio modules are not displaying this strange behaviour with the dates, then I would hesitate to say it could be your Windows' date settings (i.e. using a custom date format).

In Adagio|Reports|Report Options there are two options for formatting the dates of reports - Date format (Header/Footer) and Date format (Detail). What do they have selected here (i.e. MMM dd yyyy or ?)? Please be precise. Did anybody recently change this (in April) from what it used to be?

Other things to consider are:
- Do a Data Integrity Check in Payables. If errors are found, click the Rebuild button, then redo the DIC to see if Adagio could fix them.
- Was anything else at all changed on their PC or the Server?
- Does this occur on all Payables reports, or just a particular few?
- Is it just the Header dates that are out of whack - or do the details on the reports have strange dates as well?
- Does this occur on printed checks at all?
- Does any other workstation (if this is a network environment) display this behavior? If another station displays the same problem, then try re-installing the Adagio Payables module (before re-installing however, rename the APWIN program folder. It can be found on the drive where Adagio was installed, in the Softrak folder. If reinstalling fixes the problem, you can then just delete the old APWIN folder).
- If the problem is on this station only, then something in the environment on this station is likely the cause...check any Windows or other settings that could affect this.

Regards