Record is deleted. (Error 3167)

[Guest]

I keep getting this message when trying to run certain queries and certain
reports in my Access db. I can't find an explanation why this should be
happening. All the objects seem ok. It seems if I completely rebuild the
query then it works, but I have a lot of queries and would prefer not to
rebuild them (also when I rebuild them, the reports that are supported by
them often still do not work - so I don't want to rebuild all the queries and
reports). Any help or tips as to where to look are appreciated.

thanks, George

 

[Allen Browne]

This probably represents a corruption in the database.

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact
Test: it is possible that this fixes a problem index and the
name-autocorrect problems, and you're now done. If not, continue.

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

 

[Guest]

Allen,

Thank you very much. It looks like steps 1 & 2 resolved this for me.

I read your reporting of this bug - looks like your recommendation is to not
use this option and preferrably not use it from the start. Once again, my
appreciation. George