Identifying the Culprit

The resulting 'History' view shows all changes made to the selected row. Note in particular that the ServPrice value has been toggled back and forth several times. (You may need to scroll the view to the right to see this column.)

Select one of the rows that shows $14.95 as the price. (This view shows the value of the row before the relevant transaction was committed.)

Right-click on this transaction, and select 'Browse Transaction'. This brings you back to the browse view with the culprit transaction selected. Note that there are three panes visible in the Browse Log view:

  1. In the upper pane, view information about the transaction such as Date/Time, Transaction ID, and UID.
  2. In the center pane, view the NT User Name and Application Name.
  3. In the detail pane at the bottom of the screen, you will see the 'Old' and 'New' values of the row.

In this example, the 'UID' column of the browse pane contains the important clue (resize column if necessary). The price was changed by a process using the "PriceReview" ID.

"Ahah!" says the DBA. There is a monthly process that reviews prices and 'corrects' invalid prices. Apparently the application was not updated with details of this promotion.

Armed with this information, resolving the business problem becomes simple.

Click 'Next' to continue.