Incorrect Last Archive Date is Displayed When Archiving

Issue

Archive Transactions screen displays incorrect last archive date for a module.

Solution or Workaround

The incorrect last archive dates are caused by corrupted records in the SYAPMNT (Application Maintenance File) file.

Important
The following should only be done by a Sage Certified Consultant or Business Partner. Create a full and verified backup before proceeding. This should first be attempted in a test installation and the results should be fully verified before implementing in a live system.

To resolve the issue, follow the steps below:

  1. Open the SYAPMNT (Application Maintenance File) in Microsoft Visual FoxPro Access.
  2. Locate and identify the company (Compid) application (Applid) record with the incorrect last archive date populating the Mdate field.
  3. Delete this date.
  4. Save changes.

The next time when transactions are archived, it will populate the Mdate field with the current system date for that record. This will be reflected in the Last Archive Date for the application in the Archive Transactions screen.

© Copyright Sage Software

Leave A Comment?