1

Re: Import Wizard Violation of PRIMARY KEY constraint error

Had this error occur today:

Exception occurred in application Recorder 6 at 20/05/2008 13-48-32.
Version : 6.10.4.120

Exception path:
EOleException : Violation of PRIMARY KEY constraint 'PK__#RN_Taxon_Occurr__226FEF70'. Cannot insert duplicate key in object 'dbo.#RN_Taxon_Occurrence_Data'

I managed to track down the cause to the following being present in the Abundance column:

present,present

I removed the comma and the crash was no longer triggered.

Charles Roper
Digital Development Manager | Field Studies Council
http://www.field-studies-council.org | https://twitter.com/charlesroper | https://twitter.com/fsc_digital

2

Re: Import Wizard Violation of PRIMARY KEY constraint error

Charles,

You may have come across this one too...

When importing MapMate data; if you have either a "(" or ")" in your Abundance Data column i.e. "5Mine(vacated)", the Import Wizard will stop with a "String or binary data will be truncated" error; even though you can have the abundance term available to choose.

This one I came up against today.

Best wishes,
Les.

Les Evans-Hill
Senior Data Officer, National Moth Recording Scheme

3

Re: Import Wizard Violation of PRIMARY KEY constraint error

I got the same problem. Kirsty has just spotted "2f,2f" in the abundance column.
I'll tell you later if that solves it.

4

Re: Import Wizard Violation of PRIMARY KEY constraint error

So the tip here is, use the Data Filter Autofilter in Excel then operate the drop-down list in your Abundance column to display all the unique entries in the Abundance field and carefully check for duplicates.
It would be an idea if the import filter checked for this too.