We have a database that was being used by two different people to edit the same record at the same time. They both got error messages and now there is one record on the table that is now filled with ######. The table will no longer allow any queries to be ran against it. We figured that that table is somehow corrupt. We tried to compact and repair and that didn't work. It won't allow us to copy nor export any data from it. Are there anythoughts as to what we can do?
##### Errors across an entire record
- Thread starter Kylor
- Start date
- Local time
- Yesterday, 22:28
- Joined
- Feb 28, 2001
- Messages
- 30,328
That's a toughie.
First question, can you export anything at all from the DB, just maybe not that particular table?
Second question, when (if ever) was your last backup of that DB and how much updating has occurred since then?
Third question, have you executed your two unwise users yet? If not, I'd like the opportunity to sell tickets to the event.
Seriously, I'm rather surprised that you cannot recover data from the database after a repair and compaction. As far as I understand the way those things work, you cannot possibly have an unusable record still in the database unless they DIDN'T work in the first place. I.e. repair and compaction HAD to have failed. So that you are not working from a new copy of the DB, you are working from the same damaged file.
Try to do the repair in the way that does the operation to a file with a different name in a different folder and see what (if anything) you get. Also, if you did the repair/compaction in a macro that turns off error notification, run another macro to turn on notification, then manually do the repair and compaction.
Yup, I'd say that what you've got there qualifies immensely. Search this forum for "Corrupt Database" to see what pops up. It is not an uncommon problem. Many posters have offered solutions.
You didn't mention what version of Access you were using. That also makes a difference of a sort, because there is an OUTSIDE (and I do mean WAY OUTSIDE) chance that a new version of Access with better recovery abilities can convert the DB correctly to a higher version, after which you could export tables to .CSV files and rebuild your prior DB from those.
