Hi Sami

Restoring a Backup would be the easiest solution, I'm guessing you don't have one?

I have extensive backups

I have a backup for every day of the year going back several years

The problem is I have 48 users and going back to last night's backup means a loss of data from this morning

I fixed the problem by copying the table using Access copy

It gave an error but copied all the non-corrupted records

Awsome

Glad you mostly fixed it. I've actually been preparing a video on this and here's the checklist that I have so far...

Compact and Repair the database
Import all objects into a new blank database
Open Access first, then open the database manually
Hold Shift while opening to bypass startup code
Run Access with the /decompile switch and then recompile VBA
Debug -> Compile the VBA project
Use the command line /compact switch
Copy the file to a local drive and try again
Link to the tables from a new blank database and copy the data out
Import objects one at a time to isolate a corrupted object
Disable Name AutoCorrect
Export and reimport VBA modules as text files
Open the file in a different version of Access
Import everything into an older MDB database and convert back
Use make-table queries to copy data into fresh tables
Restore from backup

Once you know the database has corruption, I would be careful about copying and pasting objects inside the same file. Sometimes the corruption is stored in the object's internal structure, and copying it within the same database can bring the corruption along with it or even make the corruption worse.

The safer approach is to create a brand new blank database and import or link to the objects from the damaged file. That way you're pulling the good data into a clean container instead of continuing to work inside the corrupted one.

If the corruption is isolated to one table, you can often create a new table and use an append query to copy records over, which will usually skip the bad record automatically. Again, I'd do this by linking to that table in a new database.

I'll move this video up the list. You're like the 3rd or 4th person in the past few days who have said something about corrupted files.

Richard, you are the best!

Sami, I had the same problem about two weeks ago. I didn't think to try to copy the table. I just finally gave up, bit the bullet and grabbed my faithful backup. It was several days before I stopped seeing missing stuff that had to be reentered.

Sandra actually what seems to have worked very well was creating an empty database and copying the tables

Sami yeah, that's always the first thing I try after a compact and repair. And interesting enough, sometimes the corruption can be in the index and not in the table data itself. So one of the things on my checklist that I don't think I put up above is to try to remove indexes from the table. Obviously you can't remove the indexes from your primary key, your auto number, but the rest of the indexes could get corrupted too. There's a lot of weird stuff that happens.

Sami, I have done that in the past. Don't know why I didn't think about it this time. But then again I suffer from a bad case of Sometimers. Sometimes I remember; sometimes I don't.

You inspired me to move this video up the list... Corrupted!

And what a comprehensive video it was

Thank you