Duplicate records
Note: Duplicate records and SQL errors are further described in the Salesware User Guide for Advanced Users.
accesso has taken as many programming precautions as possible to prevent the creation of duplicate records. However, this is one of the most frequent causes of mayhem in Salesware, generally a result of database server crashes or power outages. A transaction is written but the index wasn’t updated because of the timing of the crash—the index doesn’t know the record exists and thus a duplicate one can be added; or the record forwarded fine but the salespoint wasn’t notified, so the salespoint keeps trying to forward a record that has already been forwarded. All Salesware data tables have a primary key, which has to be unique for each record in the table in order for the table to work properly. Duplicate records make it impossible for a data file to index properly.
Possible error messages include:
• Uniqueness of index violated.
• You have x records that have not forwarded and x duplicate records.
If you have duplicate records, contact accesso Siriusware Technical Support immediately.
Note: If you have repeated duplicate record problems, you may have the same salespoint name assigned to two salespoints. Each salespoint must have a unique name.