Compact & Repair Won't Work!

[pianoprodigy]

One of the users somehow corrupted a record. The record now has a bunch of boxes in place of the information. I tried to delete the record from the table but I get an error "The Search Key was not found in any record." When I tried to Compact & Repair, it would start the process in the bottom left corner and get about 40% of the way and just sit there (I let it go for 20 minutes). My task manager shows normal memory usage and no processor usage during the compact and repair. What is wrong?

 

[spacepro]

This might help.

http://support.microsoft.com/default.aspx?scid=kb;en-us;301474&Product=acc2000

Andy

 

[pianoprodigy]

Okay. I downloaded the Jet Database Update. I opened the GIGANTIC 30,000+ record table with the corrupted record, and the corrupted record was all blank. I tried to Compact and Repair, but it did the exact same thing. Starts to Compact with the status bar at the bottom left. It gets through 7 bars and just sits there. I went back and opened the table again, and the corrupted record looks the same (random boxes in fields). What am I going to have to do about this? Copy and paste ALL the records except that one into a new database?

 

[spacepro]

Ok.

try this.

Make a backup of your db, then delete all of the records apart from a few and keep the corrupt record in the table and try to compact and repair.

if it works then copy the records back into the table and c & R the db again.
If this doesn't work, I mean i am only guessing but if it doesn't work then post the db with just the few records.


So that we can have a look at it.

Regards

Andy

 

[pianoprodigy]

I deleted all the records except for 10 then tried to import the table into a blank database. It immediately gave me an INVALID ARGUMENT error. I get this same error if I try to CUT the record from table. It seems that this record is definitely causing this error. I wouldn't be worried about this so much, but since all this happened, I am unable to make an MDE file from a separate database that links to this one.

AISDATA.MDB is the one I'm having trouble with. It contains most all of the tables.

AIS.MDB is the copy that I edit and make changes to queries, forms etc.

AIS.MDE is the file that I generate and distribute over the network.

What's the next step?

 

[spacepro]

is it possible to post the db or email me at spaceprogram@tiscali.co.uk

While you are doing this , take a look at this.

Explanation on Invalid Argument

Andy

 

[pianoprodigy]

Should this issue influence my being able to create an MDE file on the front-end portion of the database?

Also, I am already running SR-1, and because of attorney/client privilege issues, I shouldn't post the database. Worst case scenario, what will I have to do with this?

 

[spacepro]

Understand your issues.

Your could change the data in a copy of the db, so that valuable info is not being disclosed.

Otherwise the only other option I suggest you take is this link.

http://support.microsoft.com/default.aspx?scid=kb;en-us;209137&Product=acc2000

Sorry I couldn't be more help!

Andy

 

[ghudson]

Try importing the "data" from the corrupt table into a new db. That should allow you to get all of the uncorrupted records. Then you can delete the corrupt table and import the records back.

Have your tried the free Microsoft Jet Compact utility? Click on the link below for the version of Access you are using. For more details, search the Microsoft Knowledgebase for Jet Compact. I have had a lot of success using Jet Compact to repair a db when I thought it was corrupted and Access could not repair itself.

Access 97: Updated Version of Microsoft Jet 3.5 Available for Download

Access 2000: Jet Compact Utility Available in Download Center

Access 2002: Jet Compact Utility Available in Download Center

HTH