Hello Les,

I'm sure that the problem exists in your environment. We cannot re-create it with our data here, and, as Doug points out, there are many sites not experiencing the issue. Having a programmer "see" the issue does not help in circumstances like this. They have no tools on your computers to be able to isolate the problem and step through the code.

Our Technical Support department has instructions not to escalate issues to R&D without a copy of the data that demonstrates a problem. (That's how the programmers can determine that they've actually fixed what caused the complaint, and it usually does not have to be a current copy of the data.) We don't have any data that has the problem you describe, so we cannot proceed further.

There are so many options in Adagio Inventory, OrderEntry and Purchase Orders that trying to re-create every possible combination is not worth the time or expense. Perhaps when another user runs into the circumstances and will provide their data we will be able to take a specific look at the problem. Until then, it will sit on our "issue list" in case a programmer stumbles across a cause.

After aquisition of Purchase Orders for Adagio we invested considerable time and resources in improving the manual and on-line help. We also tried to address as many of the known problem witht he product as we could in the time available. It's one of the most complex modules we are trying to maintain, and since it was developed by a different group, it's architecture is different from the other Adagio modules. This makes it a significant learning experience, and we are only aking changes cautiously because the product is fundamentally sound and we are concentrating on not "breaking" anything as we make improvements.