How to repair duplicates
To repair “good” duplicates:
1. Click on Tools > Diagnostics > Check Duplicates.
2. Use Helper and SQL scripts to sync the two versions.
To repair “bad” duplicates:
1. Click on Tools > Diagnostics > Check Duplicates and make sure these aren’t “good” duplicates.
2. Clear your Sales32c log (Tools > Diagnostics > Clear Log button), and then set Tools > Diagnostics > Log Verbosity to verbosity 5.
3. Go back into Check Duplicates. Click on the Repair button and enter daily code when prompted. This code is generated by Siriusware Technical Support representatives and is different every day.
Note: Most clients need help from Siriusware Technical Support to use the Repair button. The Repair button creates a new primary key for duplicates, so can cause your reporting to be wrong. New transactions can be created that cause your reports not to balance with actual sales.
4. The duplicates are repaired. A duplicate fix log is generated in your local Siriusware\Sales folder. It’s called duplicatefix_XXXX.txt, where XXXX is the date. You can study this log along with your Sales32c_log.txt file.
Note: Just because the “dupes” are fixed at this point, you may still have problems. For example, two duplicate pass numbers may have been printed on two different passes. Or you may have general data mix-up issues (for example, transactions attached to wrong sale_hdr). Also, reports can be wrong or present strange-looking data. If fallout like this happens, further manual repair of data may be required.