We purchased prog from former owners of the software "Purple". We are on a maintenance program for PO's. We just started to use a function of the program that we had no need for until recently. We found a bug in the program & showed it to Steve Schwartz our "go to guy". Yes, we had him log in & see on our screen the issue. He submitted it to tech support. The reply he received said had not seen that before. Ok, so maybe we were the first to find it because we verify the end result in order to make sure it is what we want & what it is supposed to be. I told him he could invite Leigh in tech support to see the issue as he saw it. After a few days with no reply, I tried to reach Leigh & was told I did not have speaking permission so I was directed to Steve Wilson. His first response was I need to send my data in. Our reply is "NO". Again I invited him to view. Leigh had asked Steve to have us run a integ check on PO & IC it was done & no errors. This was advised to Steve Wilson. He then said integ would not find this kind of issue. The issue is when modifying a PO and changing the unit price, when tabbing out of the field, the price changes for no apparent reason. It is random! Different results at different times. The fact is the price entered is changed when tabbing out of the field & therefore the extention is not correct. So my question for Andrew is, why is the first reply when an issue is pointed out & verified by a well informed person like Steve Schwartz always: it's your data, let us look at it. When we bought the prog I don't believe it came with help files & the paper manual is not informative. Steve Wilson admited to me there are issues with the program when I point out some other matters. If I am willing to take the time to show your end what the problem is why is it always, it is your data. My data has never been an issue before in like situations. My offer is still open to have either your programer or tech view the issue from my end.

Les:

We change the unit price on our PO's every day and do not have any problem with the process. Many of my clients also change the unit price regularly without issue.

If you were one of my clients the first thing I would want to do is test your data in my office to confirm that it is not your install of Adagio that is somehow causing the problem.

If the problem occurs in our office then we would want to test the program/data behavior, something that we just cannot do on line observing the behavior on your computer.

At the end of the day if we can not replicate the issue on sample data then we would need to pass the clients data to Softrak so that they can develop and test the necessary correction.

We (and I'm sure that Softrak is too) are very aware of the need to keep our clients data confidential as the best and fastest way to help our clients get problems resolved is by having direct access to their database(s).

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.

Les:

An option that is open to you to to replicate your setup in sample data. If this then replicates the issue you could provide this data to SOftrak for testing.