PO Errors

Mar 05, 2007 4 Replies

I am using RMS 1.3 with MSSQL 2000 running on windows 2003 STD with 2GB ram, Dual 2.4 Xeon, Raid 5 Server.



I have a databse that is 5GB and everything runs great except when my purchaseing manager works with Purchase Orders.



When going to commit a Purchase Order he receives the following run time error ?Run-time error ?-2147221503(8004001)?: Data has changed! Another user has updated this data record. The system cannot save your changes.? At the time of the error there is no one else even in POs. He also receives multiple other errors when the shipping guy is receiving on a diferrent po and he is going to save his PO.



I had opened a ticket with Microsoft and they were unable to come up with a solution to this error. They had me do maintenance from Admin and backup the database from Admin and restore.



This error happens on multiple computers multiple computers at random times so it leads me to believe that it is something that is happening on the database side.



Anybody have any ideas. I am willing to try anything at this point.



Thanks Jacob


Do you have any third party add-ins or custom database triggers in your system?

Glenn Adams Tiber Creek C> I am using RMS 1.3 with MSSQL 2000 running on windows 2003 STD with 2GB ram,

I get that error while just loading the items screen, or while modifying an items properties as well.

I have RMS Synergy Price Matrix Software installed. But this problem was happening before we installed that software.

There are no other custom database triggers that i know of.

Thanks Jacob

"Glenn Adams [MVP - Retail Mgmt]" wrote:

We have seen this, but it was always related to someone else editing an item that is on the PO at another machine. For instance, if we are receiving a large PO and as the items are taken out to the floor, if someone opens Manager on the sales floor and edits some information on any one of the items on the open PO, and saves their changes, then when we try to commit the PO in the back, we would get an error just like that and lose all the work back in receiving. Also, if the PO is committed while an item screen is open on the floor, and you then try to save changes made to that item, it will give you the same error and you will lose the changes to that one item. Whoever saves first wins -

I now have a rule that no changes can be made to any item from a supplier which is in the process of being received. We write a note with the specific issue, attach it to one of the items, and put it back onto the receiving bench. When the order is committed, we scan and tweak the problem items as required. We also make it a point to save the PO frequently as we are receiving it. This has all but eliminated those errors -

Tad

"Jacob156" wrote:

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required