Troubleshooting: Key violation. attempt to store duplicate value (visible to active transactions) in unique index "OPR".

When did you encounter this error?

• Immediately upon clicking the Add button.
• Upon clicking the Save button.

Immediately upon clicking Add

When you click Add, Bundle-Track automatically generates a numeric Code value for the new record. If you get this error message immediately upon clicking Add, this indicates that there already exists an Operation with the Code value Bundle-Track was trying to offer.

That default Code value comes from a generator in the database, and each time you click Add, the number is incremented one higher.

Try clicking Add again. If the next Code number is not already taken, you won't get the error. Otherwise, you will. You can either keep trying to Add until you move the generator to an available Code value, or ...

You can reset the generator to a value that is well out of the way of the Code values you tend to use. For example, if your Codes are all 3 or 4 digits long, you could set the counter to 10000, so that each new default value will be at least 5 digits long.

Procedure to change the counter value:

1. Get ISQL ready to run your commands.
   • If you don't know how, click here to learn, and then return.
      
2. Copy and Paste the following code into ISQL:
   

   set generator genoprlab to 10000;

   • Note: You may modify that statement to specify any other integer.
      
3. Execute. (Click the lightning bolt icon.)
    
4. Exit ISQL and IB Console.
    

Upon clicking Save

Which action were you performing?

• Editing an existing Operation.
• Adding a new Operation.

---

Editing an Existing Operation

This indicates that you have changed the Operation's Code to an unavailable value. Bundle-Track then reverted the Code to the previous value and left the Operation Editor open.

If you really want this Operation to have the Code that appears to be unavailable, you need to resolve the conflict. Begin by looking in your Operation List for an Operation with this Code:

• If you find an Operation with this code, then you've found the problem: that Code is already being used. You need to choose a different Code for your new Operation, or rename the other Operation first.
   
  
• If you do not find an Operation with this Code, you can safely conclude that an Operation having that same Code previously existed and has since been deleted, but remains hidden in the database to preserve data integrity. To make that Operation Code available again, you will have to rename the old deleted Operation as follows:
  1. Restore the deleted Operation. (Here's the procedure.)
  2. Edit that restored Operation to change its Code (perhaps by appending "OLD" to the current Code.
  3. Optionally, delete the old Operation again.
  4. Edit your other Operation as desired.

---

Adding a New Operation

When you get this error, the Operation Editor will remain open, but the Code will not be the one you specified. Examine the other details in the Operation Editor to determine whether you are looking at the same Operation you were just editing, or at a new empty Operation record.

• If it looks like a new empty Operation record, then the Operation record you just saved is fine. (If you exit the Operation Editor, you will find your new Operation in the Operations List.) Why the error then? Well, when you Save a new Operation, right after the save process successfully finishes, Bundle-Track automatically starts the process of adding yet another Operation. The appearance of this error at this moment indicates that the default Code generated for the next new Operation was unavailable, just as sometimes happens when you click the Add button (as explained above).
   
• If it looks like the same Operation record you were trying to add, then this error indicates simply that the Code you specified for this new Operation is unavailable, and your new Operation has not yet been saved. For now, to enable yourself to save your new Operation record, specify a different Code - you can change it later. The details and resolution options are the same as those for Editing an existing Operation (as explained above).

We welcome your comments at support@bundle-track.com.

If you would like our live assistance, you may hire us at our professional services rate.