RE: Figuring out what field is causing key violation on append
- From: KARL DEWEY <KARLDEWEY@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 20 Feb 2009 15:00:01 -0800
I would start by letting it append those that it will and then run an unmatch
query to see what was not appended.
Use input table left join to new table with criteria for new table join
field as 'Is Null'.
First look for nulls.
Then duplicate records.
--
KARL DEWEY
Build a little - Test a little
"JN" wrote:
I have a new version of a program. It has pretty much the same table.
design, except for a couple of extra fields and a few fields got an
increased in size.
I want to just copy my data from my old table into the table in the new DB
(SQL 2000 back end) however when I do I get the error:
Microsoft Office Access can't append all the records in the append query
Microsof Office set......and did not add XX records to the table due to key
violations, .......(all other than key violations is 0)
This table has about 75 fields. A lot of them in the previous version were
set to Required = No and other minor changes. It would take for every to
find the right combination so is there a way when I run an append query to
see what field(s) is causing the problem?
- Follow-Ups:
- References:
- Prev by Date: Figuring out what field is causing key violation on append
- Next by Date: Re: Multiple Donations - Mail Merge
- Previous by thread: Figuring out what field is causing key violation on append
- Next by thread: Re: Figuring out what field is causing key violation on append
- Index(es):
Relevant Pages
|