Corrupt Record in Access Table

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

punster

Thread Starter
Joined
Dec 23, 1999
Messages
33
A record in the table has gotten very corrupted with garbage data. I have tried every trick I can think of to delete the record from the table - and no matter what I do I get the message "Search Key not found in any record" I have gone through and changed the data for all relationship fields, but then I get the message "Invalid Argument". I have tried deleting the relationships and I have also tried deleting all the data on the record and still can not delete the record itself. I even tried writing a delete record query, but that also failed with the same error. Then I tried to copy the table so I could try to get rid of the record by forcing a duplicate, but it won't even let me make a copy of the table - when I try to paste I get the "Invalid Argument" error. Anybody know any tricks as to how to get rid of a corrupt record?
 
Joined
Jan 11, 2005
Messages
36
To Punster:
My money says your using referential integrity and i know all the ac export
say thats what it is for, well you got lesson one, never use it. What i'm
speaking about is table analyze. But to solve the sticky wicket your in
try the following steps:
1. create a blank database.
2. close the database for now
3. open your original database
4. look under tools - relationships
5. remove your relationships
ps. if it were me id leave them undone, but thats where me and
ac exports differ in opinion. I've been using ac since 1.0 and
was sucked into to misbelief by book writers with no real world
experience and payed a heavy price for stupidity. I handle all
referential integrity thru query's and programming. But i never
built a database with less than 50 or more tables either, thats
the real world.
6. now close the database
7. open your blank database and recreate the table with fields
manually and do not create any key fields for now. Save table.
8. now open the original database with blank still open and open
the table in datasheet view. highlight and copy say 20 records
at a time and then do a paste append. close the table and then
reopen and to make sure there are no bad issues. If none continue
till all records are transfered.
9. now here is the tricky part, i would close the new database and
then delete the table from my original database, close then reopen
the database and import the table from the blank database. If old
murphy is smiling things should work fine from that point on.
10. If you still are getting errors then close the original database and
starting with tables import them into the blank database, then
your querys, forms, reports, macros and so on. Do not try to do
this whole hog that is everything at once or old murphy will crash
your party.
Thats how to resolve bad things in ten easy steps, i experienced the
same issue one time upgrading from that bad ac97 version to ac2k.
Believe me ac97 was nothing to brag about, drove the ms/ac tek support
up a wall, they hated to get ac97 calls at the time, always suggesting, you
do a upgrade. Anyway I hope this bit of advice helps, flixx.
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Staff online

Top