Enhancements & Revisions



Adagio Ledger 9.0C


November 24, 2010



    General Ledger

  • If Next Year has been created, a retained earnings account can no longer be changed from single to multi-currency and the retained earnings account can no longer be changed in departments or in the company profile, as doing so resulted in incorrect balances after posting or unposting. These changes are allowed again once the current year has been closed.

  • When you copied an account to a new account with a lower account number (higher in the grid) than the account being copied, the account you were copying from was opened for edit instead of the new account.

  • When editing budgets using '% increase' for the Update Method, or using Moving Values by '% increase', the resulting figures were 100% larger than they should have been.

  • A warning message was added in Ledger 9.0C batch entry if the date of a transaction is outside the date range of the fiscal period it is assigned to. This warning now only displays once per entry rather than for each detail.

  • If 'Edit retrieved entries' was set to 'No editing permitted' in the Company Profile and you attempted to edit a retrieved batch, if after getting the warning saying modification is not allowed you tried to view a detail anyway, an error message was displayed.

  • If you had Next Year open and had posted transactions to an account, then changed that account from single to multi-currency, further postings to the account caused an integrity error that could not be rebuilt by the Data Integrity Check.

  • An error occurred if you provisionally posted more than 20 batches at one time.

  • An access violation error message was displayed by the Batch Unpost function if you closed the function without unposting or if the 'Auto print posting journal after post' option was on and you unposted (note: the batch was correctly unposted in these cases).

  • The Unpost Batch function now handles the case where it previously gave an error if an unposting journal file existed for next year but next year was not open. This likely occurred due to an improper restore procedure (all GL data files were not deleted before restoring).

  • Some accounts did not show an opening balance on the Detail Listing when printed in Source and Home format.

  • The Report Balance total field at the bottom of the Detail Listing report was incorrect in some cases when it was printed for multiple departments and it included accounts for which the only transactions were from prior years.

  • If you posted to the YE Adjustment Period for the prior year, an error batch was created if the period specified in the batch was for a closed period in the prior year. This no longer occurs.

  • The new import/export engine used to interface with Excel in Ledger 9.0C gave an error during import if the number of columns in the import file and the template did not match. The error is no longer given if the number of columns in the import file is greater than the number in the template, as users may create a spreadsheet with more columns initially and then delete the values in the columns rather than deleting the actual columns.

  • In version 9.0C, if you defined the Amount field incorrectly as string instead of number in a batch import template using the ASCII Fixed Length format, all credits were imported as debits.

  • Importing the 'Multicurrency' flag set to true to change existing accounts to multi-currency caused a database integrity error when posting to these accounts.

  • When you exported accounts containing an "E" in the Account number to an Excel file (e.g. "21E082"), they were interpreted as an exponential number in Excel (e.g. 2.1E+83). Accounts are now formatted as strings rather than numbers when exported to Excel.

  • If an Adagio User belonging to a Security Group that does not permit them to log in attempts to log in, messages are no longer displayed related to retrieving batches on start up.

  • An entry as been added to the end of the Data Integrity Check (DIC) log when a rebuild has been done. It now says "After doing a Rebuild you must run the Data Integrity Check again to ensure all errors have been rebuilt". In particular if a rebuild is done and the log contains the entry "Posting file merge completed", you need to run the DIC one more time to complete the rebuild. In general, it is good practice to run another DIC after a rebuild. In cases where the DIC cannot rebuild the database, the entry " Data may require repair. Call your dealer or Softrak Systems for Data Repair Service." is added to the end of the log. Although the data may still be useable, you may want to restore from backup or have the data repaired, as errors in the database may cause problems at a future date.

  • The workstation install (WKSETUP.EXE) and the auto-workstation install for Ledger 9.0C (2010.05.11) incorrectly set the path to the Ledger.EXE file in both the Windows start menu and desktop icon to the local C drive instead of to the network drive in some cases.

  • The workstation install did not add entries for the Ledger program in the Windows start menu if you installed 9.0 and Ledger 8.1A or older was also installed.

    Financial Reporter

  • You can now display the Chart of accounts summarized by any text field, as well as in account number order. By populating an option field with an alternative account number, you can choose to display your chart in another sequence. This may be useful in creating statements according to a different coding structure.

  • Users with Print Only access can now reset their toolbars and access the options on the View | Customize menu. The fiscal period and year will always be displayed on the Toolbar.

  • GLUPDATE did not work for the last column in the statement (usually period 12 or 13).


© Copyright Softrak Systems Inc. All rights reserved.