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

Thanks Francisco,

We're copying all records to a new table (less the bad key).

BTW, my previous post was misleading.  We are allowing the autonumber to
generate the key.  'via code' was meant to say record add/update was via
code (not the key itself).

Thanks Again,
Ron



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Francisco H
Tapia
Sent: Monday, March 22, 2004 10:50 AM
To: Access Developers discussion and problem solving
Subject: Re: [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


-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com