[AccessD] Error in Access 2003 that I've never seen before

I tend to agree, but two puzzles remain (purely in an academic sense -- I
don't play to lose sleep over them).

1. The data can't be corrupted since the "bad record" copied intact to the
Saved As table.

2. With all the indexes removed, why was it doing an ISAM Seek? One would
have thought that in the absence of indexes, it would be forced to do a
table scan. Perhaps that just reveals how little I understand ISAM tables.
LOL.

Arthur

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: June 25, 2005 2:07 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Error in Access 2003 that I've never seen before

Hi Arthur:

It could be that the record you are trying to delete is not being referenced
properly; either the field named used is not correct or the table is
corrupted. It would be caused if the table index did not matching the table
data. I have only seen it once and I resolved it by exporting all the data
into a new table, deleting the old and then renaming the new table. Using
that method excluded a coding or table structure error. Conclusion; Either
the data or index was corrupted.

HTH
Jim