Problems Changing/Deleting Corrupt Entry...

[Goobz]

I have one entry that got corrupted on my BE database.

It won't let me change, delete, or modify the entry in any way, shape,
or form through trying to do a table edit.

Is there a way to "force" the record to either delete or change?

As of now, I get a "The Search Key Was Not Found In Any Record" error
when I try and make any kind of change, or a "delete record".

Help would be appreciated!

 

[Pete D.]

Copy and paste the table design only then try and run a append query of all
records from old to new. If it works don't forget to fix relationships. Of
course make sure your doing it all on a copy of original.

 

[John W. Vinson]

I have one entry that got corrupted on my BE database.

It won't let me change, delete, or modify the entry in any way, shape,
or form through trying to do a table edit.

Is there a way to "force" the record to either delete or change?

As of now, I get a "The Search Key Was Not Found In Any Record" error
when I try and make any kind of change, or a "delete record".

Help would be appreciated!

See Tony Toews' corruption FAQ:

http://www.granite.ab.ca/access/corruptmdbs.htm

In short you will need to create a new backend *DATABASE* - this one is at
best suspect; import all the tables except this one; import this table, design
mode only. Link to the current backend and run one or more Append queries to
append all records except the damaged record into the new table. The query
criteria cannot "touch" the damaged record in any way - i.e. if the PK of the
record is 4121, don't use

<> 4121

in the criteria; instead use

<= 4120 OR >= 4122


John W. Vinson [MVP]

 

[Goobz]

See Tony Toews' corruption FAQ:

http://www.granite.ab.ca/access/corruptmdbs.htm

In short you will need to create a new backend *DATABASE* - this one is at
best suspect; import all the tables except this one; import this table, design
mode only. Link to the current backend and run one or more Append queries to
append all records except the damaged record into the new table. The query
criteria cannot "touch" the damaged record in any way - i.e. if the PK of the
record is 4121, don't use

<> 4121

in the criteria; instead use

<= 4120 OR >= 4122

             John W. Vinson [MVP]

This worked PERFECT! Thank you for the example on how to not include
that record as well.

 

[juergsman]

This worked PERFECT! Thank you for the example on how to not include
that record as well.

John, you are a hero....... had the same problem and until I came
across your suggested solution (excl. in the criteria the affected
records). Worked just fine. Thanx man.