I've been getting this error when I try to print reports in inventory. Particularly the transaction history report. When I get the error it hangs up Agagio and I am forced to close inventory and reopen it.

Hi Clint,

These sorts of formula errors in reports typically occur because the program, report and data dictionaries are not all in synch. There are no known problems with printing reports in Inventory 9.2A and invalid formulas.

What version of Inventory are you using? From the image you included, it is version 9.2A as from the logo, but the release date would be handy.
Do you use Adagio MultiCurrency?
Do you recall the last time you were able to print reports from Inventory successfully? What have you done since that time? Install any Adagio upgrades? Windows system updates just installed this week.

You may want to get in touch with your Adagio consultant, if you haven't yet already.

Hi,

The version we are using is 9.2A (170608) and continue to get the <bMultiCurrencies> Error in inventory when trying to print transaction reports

We do not use MultiCurrency.

I am told this has been a problem since September or October of last year.

We are getting another dialog box every time order entry is opened. It says that document statistics is incorrect and will be updated. Its more of a nuisance than anything else, but that ones been a problem since early 2015.

I've talked to our consultant several times about both these issues and he has pointed me here. I've just failed to be persistent at getting this resolved.

Thanks!

Hi Clint,

Using the same version of Adagio Inventory as you, and previewing the Transaction History report on sample data for just shipments (as you did) or other selections, I was not able to replicate a problem.

Are you able to replicate the same error in Adagio Inventory sample data? Just to confirm whether the issue is with the setup or the data.

If single-currency sample data also gives the same error, then these are the correct files that should exist on your system:
- \Softrak\Inventory\Inventory.exe dated Jun 5, 2017
- \Softrak\Dict\ files @N92AI.SSI and @N92AR.SSI both dated May 30, 2016
- \Softrak\Inventory\StandardReports\ICtransh.rpt dated Jun 24, 2015

If I edit this RPT file with the Crystal Reports designer program, I see a formula <bMultiCurrency> in the report, though I don't know exactly how it is used. It looks like a true/false variable.
And this report is based on a temporary work file, so a successful print of this report presumes that the data passes an integrity check, and this work file gets created successfully.

If you have a \Softrak\Inventory\ModifiedReports directory with the same report file ICtransh.rpt in it, this would mean that someone has saved a modified version of the Transaction History report for you. If the file date is older than that above, it is based on an earlier program version and would require updating with the new reporting environment. I don't suspect this is your scenario, but it must be mentioned.

--------

As for the other Order Entry message you are getting, regarding document statistics being updated, this message would appear if the stored order count is different than the number of records to be displayed in the grid, when Enter Orders is first opened. This message is here for legacy reasons, and should never appear now unless there were problems in the hardware or network environment, not allowing correct values to be saved with the data. My belief is that something is going wrong with your system, either on a particular workstation or the network environment. If so, I wouldn't be able to assist over this support forum, and that would need to be investigated with your Adagio consultant and IT support. Anti-virus software may also be a culprit.

What version of Order Entry are you using? I presume 9.2A, since Inventory is also at that version, but this needs to be confirmed.

Hi Clint:

How are sales orders entered into OE? Are there any methods other than manual keying of orders such as EDI processing?

Thanks for the quick response!

I can replicate the error in the sample data.

The only file that doesn't match is the: \Softrak\Inventory\StandardReports\ICtransh.rpt dated Jun 24, 2015
It is date Dec 5, 2015

I do not have the \Softrak\Inventory\ModifiedReports directory

As for Order Entry we are using 9.2A 160707

And Bruce, the only way we enter sales orders manually.

Thanks,

Clint

Hi Clint,

Since your report date is newer than what it should be, this means to me that either someone has modified this report, or some previous installation mis-dated this report, and a later upgrade or service pack was not able to overwrite this file with one that had an earlier date. In either case, this would appear to be the culprit.

If you have a \Softrak\Inventory\Backup folder and in one of the sub-folders, this ICtransh.rpt with the correct June 24, 2015 date, you can try replacing the wrongly-dated report with the good one. If you don't have this report file in a backup folder, then you should contact your Adagio consultant and they could do this replacement for you.
---
If you don't have any external process for adding/deleting orders, such as EDI or automated import, then my first suspicion is bad hardware/network. Easy for me to say, to be fair.

I've reached out to our consultant for help with the report, and hopefully that resolved the error.

-----

I'm thinking that the miss-match could come from when I deleted some obviously corrupt data using GridviewRW at the suggestion of our adagio consultant. I feel if it were a hardware or network issue it would be hard to miss over last 2 or so years this has been happening. Is there any course of action you can recommend in diagnosing the problem.

Thanks,
Clint

Hi Clint

Using GridViewRW is asking for trouble. It can corrupt the data in ways that defy the imagination unless you know exactly what you are doing. If a client of mine used it, found a problem, and then didn't immediately restore from a backup, I would yell at them. I have a feeling Softrak feels the same way, although they have to be more tactful.

In the future make sure to state that you used GridViewRW on the data up front so that those of us who might be able to help know what we are dealing with.

Steve

I'm fairly certain I deleted data in GridviewRW around April of 2014. I'm being told by my users that this Order Entry popup has been a problem since 2015. It seems hard to believe that it would take a year for the error to rear its head.