Finding Mis-Matched Transactions

In a distributed multi-user database environment such as the one Trak Pro operates in, there can be instances where under heavy network loads, or during equipment or server failures, your database may not be updated correctly. A workstation may fail to commit updates if Windows locks up, or your server might not post database changes promptly after signaling the POS workstation that everything was OK. These events could lead to conditions where a Transaction Header Record does not match the detail items of that transaction.

If you suspect you are having database networking issues, you can execute this diagnostic procedure, called the FIND MIS-MATCHED TRANSACTIONS check. This can be found in the DIAGNOSTICS Menu, if you are logged in as a user with Diagnostics rights.

This procedure does the following:

The computer will scan all Transaction Records and check:

Does the Transaction Header Total EQUAL the SUM of the Transaction Detail Items associated with it?

After you run a Check for Mis-Matched Transactions, you will be able to identify (and therefore respond to) any potential customer complaints that might exist. In the example above, what you see is the result of a TEST SCREEN SHOT, where we FORCED transactions to be “out of sync”. In a NORMAL Check, you would typically see NO PROBLEMS.

Please bear in mind that you SHOULD NOT have problems of this sort under normal operational conditions. If you are consistently getting errors reported with either the Reserved Seating Integrity Check, or the Find Mis-Matched Transactions Check, then there are problems with either your network topology, server settings or SQL components that need to be addressed. This is intended as a diagnostic tool, and a remedy of last resort.

Related Topics:

See Also:

Reserved Seating Integrity Check
Failed Internet
Transaction Viewer
Transaction Searches