Enhancements & Revisions

Adagio OrderEntry 6.8A

June 20, 2002

Enhancements have been made in the Data Integrity Checker. More types of phase 1 errors are detected and can be rebuilt. Files are compressed during rebuild by removing deleted records. This reduces the size of files and speeds up the integrity check. Progress is now shown during the time the program is checking the free list, which can be considerable for files with a large number of deleted records. These enhancements were made in the Adagio Data Source (ADS), and will be present in all Adagio applications when the updated ADS is installed by Adagio OrderEntry.
An error occurred while printing or previewing documents in the Designer if your printer driver had more than 64 different paper sizes.
The ‘Average number of days between orders entered and invoicing’ on the Summary Statistics report was incorrect in some cases.
Import orders did not allow comment lines to procede item detail lines in an order in the import file. This caused a problem at some sites when importing orders from RemoteDesk™.
Dayend caused an integrity error in Adagio Inventory if a credit note was posted for a LIFO/FIFO item before an invoice was posted for the item, all costing lots for the item were empty, and the quantity on hand was allowed to go negative.
Forms were faxed to the wrong customer fax number in some cases when the fax queue was used. This was a timing problem on some machines and very rare.
When Adagio OrderEntry was installed, the order and invoice number finders on the order, invoice and credit note post screens stopped working in ACCPAC® Plus™ Order Entry 6.5A.
Deleting a customer in Adagio OrderEntry now deletes any associated ship-to addresses on file for the customer. Customers with ship-to addresses should be deleted in Adagio OrderEntry rather than Adagio Receivables.
When issuing a credit note for a miscellaneous charge, the transaction date you assign is now used instead of the session date.
If a document containing a miscellaneous charge was re-printed from history, and the option 'Print Miscellaneous Charges Last' in the Company Profile was selected, an error occurred.
The Tax Base and tax fields in the Tax Tracking report were positive instead of negative when a credit note was posted and the tax ‘On invoice by’ option in the Tax Group was set to by ‘Line item’.
When entering orders in databases using single segment item numbers, where the maximum item number width was less than 16 characters, a warning incorrectly indicating insufficient quantity available was displayed for items of the maximum item number width.
Credit notes added the amount to the Tax Base on the Tax Summary report instead of subtracting it.
Costing was incorrect in some cases for items using LIFO/FIFO costing where a costing lot had negative quantity but positive cost.
When importing Ship-To Addresses from an Excel® spreadsheet, blank cells in the import (such as unused address lines) caused an error.
There was a problem displaying documents in the history grid when changing tabs from the Reference tab if documents were displayed sorted by customer.
When items with alternate units of measure, using moving average or standard costing, were invoiced for more than the quantity on hand in inventory, it caused the costing of items in the GL batch and on the audit list to be incorrect.
If another application installed the Crystal Reports 8.5 print engine, there were intermittent problems printing reports on some machines.