Primary key violation when importing payroll numbers from an older version of CertPay Wizard
Q) When importing payroll numbers from an older version of CertPay, I get a Primary Key violation. What causes this and how can I get around it?
A) This issue is caused when a payroll number in an older version of CertPay is not a numeric value after stripping out the payroll number prefix.
As an example, if your payroll number was 2005-33-888-333 and no prefix is used, CertPay has to determine a numeric value to use for the payroll number in version 5. If for some reason the payroll number it calculates matches an existing payroll number the primary key violation appears.
Release 5.0.0.8 resolves this issue by stripping all non-numeric characters from the payroll number after removing the prefix. If the resulting number is too large to use, the internal number used in the older version of CertPay is used instead.
Comments are not allowed for this entry.
