Error:120 Lookup item not found::Formulas.Name:=IncludeClosingAmts

The error appears when clicking the Print or Preview button on Detail Listing. I have tried it in XP and Windows7 computers, with and without sample data, including one period or one year, one range or no range and it always fails.

Another client had a similar error in AR and we were told to do a clean install of AR. This is not going to work since our client want to access older databases with older versions of AR and GL and so do we.

Hi Patricia,

This 'error 120' is due to the program and report file being out of synch, and could also include the report table. An expected report variable being sent from the program could not be found from the (typically) older version of the report. Your installation is not set up correctly, which is why the instructions of doing a clean install was provided.

Do you use a ModRP modification of the Detail Listing report? If so, your modifications will need to be re-done to the most current RPT files from the \Softrak\Ledger\StandardRP directory to accommodate the updated report variables.

If you need to work with older versions of Ledger (or other Adagio programs), you can install them to a separate program location, such as X:\90C\Softrak\Ledger, where a different location of the root Softrak folder will keep things separated from the current versions.

Why does your client need to open the data with older versions of AR and GL? I can understand consultants needing this to support clients that haven't yet upgraded.

Hi, Patricia,

There is probably a mismatch between the report and tables at the site. The solution really is to do a clean reinstall of the product that is giving the error.

I'm curious though, why wouldn't they just update the data to the current release when next they need to access it? Or, if this is Ledger, they/you could Import Prior Year Data?

Having multiple versions of a product installed at an end user site is not a supported configuration.

The Ledger error was created by a ModRp and the AR issue seems like it was as well. Our clients have older versions of AR and GL to open previous years backups. It avoids going to the hassle of having to convert the database if they need to access older data. We never know who and when this will happen.

The install process keeps the older version of Ledger (8.1A) and Receivables (8.1A). There is nothing wrong with using the older version for older backups is it?

Hi, Patricia,

In those cases, no. You didn't clarify this at all earlier. Many would think it is more hassle to remember which version of a program to run when accessing particular data and would find it much easier to just convert it all to the most recent version as it is accessed.

The reason the install maintained Ledger 8.1A is so a site could edit their older data (probably to ensure year-end adjusting entries were entered) without inadvertently converting the data to Ledger 9.0x. The purpose of this would be so the site could then use the Import Retrieve Prior Year Data on the older data. As you know, the data must be pre-9.0x data to use the function. Thereafter, the data would have been converted to the newer version and accessed within the newer module. At this point, the older version could be uninstalled as it is no longer necessary at all.