[AccessD] Can't Delete a Bad Autonumber Key:

One solution is to import everything into a new table and simply omit 
the record you don't want imported something like in the where clause 
like...

Where ID <> 212736

(by the way... its typically safer (less corruptions) to allow JET to 
create the autonumber.)
Hths

Ron Moore wrote:

>We have a A2K Repairs DB where an autonumber key is generated via code
>from our Customer Service DB.  The Repairs DB has a bad key (212736)
>which cannot be deleted (last good autonumber key is 919).  Error
>message reads, 'The search key was not found in any record'.  Cascading
>Delete was turned off and we still get the error.  The updates &/or
>creations are no longer taking place.  
>  
>
-- 
-Francisco