In Sales
The clearest indication of duplicate records in Sales is the error message, “CMainEngine/ForwardAllFiles: Forward of Duplicated Record. Tableupdate()Error #1884 - Uniqueness of index SALE_NO is violated. SALE_NO Alias SALE_HDR.”
If this error messages occurs in Sales or if any other behavior indicates that duplicate records exist, try these steps.
Fixing “good” duplicates
“Good” duplicates are identical records - the server has received the records but the salespoint wasn’t notified and so is trying to forward them a second time. This generally happens if Sales was interrupted somehow during the forwarding process, so the records forwarded but the server didn’t notify the salespoint that the records were received.
1. Go to Tools > Diagnostics and click the CheckDuplicates button.
2. The number of duplicate records on your salespoint is displayed in the box.
3. Click OK.
4. Click the CheckDuplicates button again. If the number of duplicates is now 0, it means you had all “good” duplicates and they are now fixed.
Note: If the number is now anything greater than 0, it indicates you have some “bad duplicates.”
Fixing “bad” duplicates
Bad duplicates are records with the same key field value whose other record information differs. In this scenario there are actually two different records that somehow ended up with the same key field value. In order to preserve the data, the second key field needs to be assigned a new and unique value. In this case, call accesso Siriusware Technical Support. You are most likely be directed to run Repair Duplicates and Get Max Keys on the salespoint. To run Repair Duplicates on a salespoint, you need a special code from accesso Siriusware Technical Support.
Note: Do not use the code for any other or subsequent tasks without checking first with accesso Siriusware Technical Support.
This utility generates new key field values for duplicate records and attempts to repair any affected records. It also generates a report of what was done to repair the situation and accesso Siriusware Technical Support needs that report from you.
Note: In extremely rare circumstances, due to duplicate guest numbers, links between guests and parent guests may be severed in the repair process to eliminate duplicates. Neither Gst_log nor Gst_book are repaired in this process, which very occasionally may result in the loss of Guest preferences and how many times passes were printed for guests who were repaired in this process.