Re: Primary Key constraint error
- From: "Olaf Engelke [MVP Windows Server]" <oenews01@xxxxxxxx>
- Date: Mon, 11 Jul 2005 12:56:36 +0200
Hi Dan, Dan Slaby wrote:
I am pretty sure, you wanted this question have posted in a different newsgroup (Access, SQL server?)I am importing data from one table to another using the import wizard and sql query. However, I use an 'in (nbr, nbr)' to select data. When I use the in clause, I get an error on the last row that terminates the statement because it violates the Primary Key constraint. However, querying the destination table, the Primary Key does not exist. When I use the '=' for the very same individual record, the data copy succeeds. Is there a problem using the 'in' with the import utility? I imported the records to a table and tried to import from that table with the same error. The Primary Key values I am trying to import do not exist in the destination. Any suggestions why this might be happening?
Between could it be, that the key you want as primary has already duplicate appearances in the source table?
Best greetings from Germany
Olaf
.
- Follow-Ups:
- Re: Primary Key constraint error
- From: Dan Slaby
- Re: Primary Key constraint error
- References:
- Primary Key constraint error
- From: Dan Slaby
- Primary Key constraint error
- Prev by Date: Re: Slow login to server
- Next by Date: Re: WSUS client didn´t download/install Updates from WSUS Server
- Previous by thread: Primary Key constraint error
- Next by thread: Re: Primary Key constraint error
- Index(es):
Relevant Pages
|